On 1/25/08, Olivier Lefevre <[EMAIL PROTECTED]> wrote: > By the way, won't all this pretty much require that Octave be > available in shared lib rather than executable form?
This is indeed already the case: octave.exe, octinterp.dll, octave.dll and cruft.dll. > Seeing > that octave.exe is just 5.5K and there are megabyte-sized > libraries under lib, I assume this is already the case but > what is the difference between octave.lib and octinterp.lib? > Which one do I need? And what is cruft.lib? cruft.[lib|dll]: mainly FORTRAN code implementing low-level computation routines octave.[lib|dll]: octave C++ library (matrix classes, file system operations...) octinterp.[lib|dll]: octave interpreter library (defines the various octave interpreted types, m-file parser, builtin functions...). The file __java__.cc (from the java package) already links against these 3 libraries (it's the default when you compile with mkoctfile). So if you put your code into that file and compile with mkoctfile, you don't need anything else. Michael. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
