Re: Mingw Octave-3.4.3 binaries for testing on windows

[PhilipNienhuis]

nitnit wrote:
> 
> 
> PhilipNienhuis wrote:
>> 
>> 
>> File classpath.txt can also be put in the user's home dir, or in the java
>> pkg script file dir (share/.../java-1.2.8/ ) 
>> Contents of file "classpath.txt":  (Note: Adapt path settings to your
>> system!)
>> 
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\poi-3.7-20101029.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\poi-ooxml-3.7-20101029.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\xbean.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\poi-ooxml-schemas-3.7-20101029.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\dom4j-1.6.1.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\jxl.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\OpenXLS-6.0.6.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\odfdom-java-0.8.7.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\xercesImpl.jar
>> X:\Octave\Octave3.4.3_gcc4.5.2\lib\jOpenDocument-1.2.jar
>> 
>> This will load the java class libs required for spreadsheet I/O in the
>> static javaclasspath.
>> 
>> Alternatively, the io pkg function "chk_spreadsheet_support.m" can do
>> this too but then in the dynamic javaclasspath.
>> 
>> 
>> 
> 
> What will happen if I will simply put these jars in the
> /share/.../java-1.2.8 or the /lib/octave/packages/java-1.2.8 ?
> In that case, do I still need a classpath.txt ?
> In any case I think that running chk_spreadsheet_support is easier since a
> simple 1-2 lines script can set the prefix and the correct class. Other
> wise, in order for the installation to remain portable, the classpath.txt
> should be generated as a 'post install' procedure !
> 

On my Mandriva system I find lots of .jar files in /usr/lib.
Not unexpected as these files *are* libraries. That's why I've put them in
(msys) /lib.
Another reason is that -theoretically- these files may need to be used by
other progs.

As to classpath.txt / chk_spreadsheet_support:

- classpath.txt is for more static environments.

- chk_spreadsheet-support is easier, but you'd still have to check if the
java package is loaded (!), then infer the directory where the jar files
reside during startup of Octave, process this into some string, and feed
that string to chk_spreadsheet_support. It's doable, but perhaps too
involved.

- You can also have a look at how it is done in the 3.2.4 MinGW binary.
Benjamin also put the jars in /lib, and used PKG_ADD to add them to the
javaclasspath; have a look in 
/libexec/octave/packages/java-1.2.7 
to see how he did it.

Once your binaries have ripened enough we could think of building an
installer out of it. That installer could figure out what packages to
install, and set up all paths & javaclasspath & classpath.txt.
Such tasks are ideally done in an installer.
A while ago (several months) I saw a message in one of the Octave MLs by
someone who offered to volunteer for helping out with building an installer


Philip

--
View this message in context: 
http://octave.1599824.n4.nabble.com/Mingw-Octave-3-4-3-binaries-for-testing-on-windows-tp3928387p3933116.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.