Re: Mingw Octave-3.4.3 binaries for testing on windows

[nitnit]

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 ! 

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