Erik Adli schrieb:
> Hello all,
>
> On Mac Os X 10.5.2 we have installed the sourceforce package
> octave-3.0.0-i386.dmg. The package works perfectly out-of-the-box when
> run normally (from terminal or from icon).
>
> However, we are building a progam where octave has been embedded, using
> mkoctfile. It seems that the octave-3.0.0-i386.dmg file provided for
> some reason points to a non-existant directory:
>
> /tmp/dependencies-386/....
>
> instead of the installed location
>
> /Application/Octave.app/Contents/Resources/....
>
>
> mkoctfile does not work because of this, unless you either update the
> paths in octave-config, or eventually put a soft link in /tmp (
> /tmp/dependencies-386 -> /Application/Octave.app/Contents/Resources )
>
> Running the program does not work either, without the soft link.
> (
> ./placet-octave
> dyld: Library not loaded:
> /tmp/dependencies-i386/lib/libreadline.5.2.dylib
> Referenced from:
> /Users/eadli/work/myPlacetDev/placet-development/src/placet-octave
> )
>
> The soft link in tmp saves the day for me, but I wonder if the
> octave-3.0.0-i386.dmg shouldn't rather be provided with the correct
> default Mac OS path in order to avoid these problems for future users?
>
> Best regards,
>
> Erik Adli
Hi Erik,
are you using
/Applications/Octave.app/Contents/Resources/bin/mkoctfile-3.0.0
instead of
/Applications/Octave.app/Contents/Resources/bin/mkoctfile
or is it "octave-config" that does not do the right thing?
With Octave.app "mkoctfile" isn't a link (like eg. on Linux) that points to
"mkoctfile-3.0.0", but it is a script for itself which (hopefully) is driving
"mkoctfile-3.0.0" correctly - at least I've never had a problem on my machine
before. "mkoctfile-3.0.0" is unchanged when the sources are compiled and that's
why a "mkoctfile" has been created that should overwrite all internal variables
of "mkoctfile-3.0.0". Can you please verify that you are using "mkoctfile"? The
"mkoctfile" is a normal shell script that you also can easily modify with a
text
editor if you want to change some things...
I am using the same trick to startup Octave itself (either by double-clicking
the icon or from command line), there, also the /tmp/dependencies-i386
occurencies are redirected to the right place...
Eg. if I call "mkoctfile-3.0.0" printing the variable LFLAGS then the output
points to /tmp/dependencies-i386
~/Desktop/Octave.app/Contents/Resources/bin/mkoctfile-3.0.0 -p LFLAGS
-L/tmp/dependencies-i386/lib/octave-3.0.0 -L/tmp/dependencies-i386/lib
Now let's do the same thing with "mkoctfile" instead of "mkoctfile-3.0.0"
~/Desktop/Octave.app/Contents/Resources/bin/mkoctfile -p LFLAGS
-L/Users/Thomas/Desktop/Octave.app/Contents/Resources/lib/octave-3.0.0
-L/Users/Thomas/Desktop/Octave.app/Contents/Resources/lib
you see, the paths to the lib dirs are correctly redirected.
BTW, the path /tmp/dependencies-386 is used to install Octave and all its
dependencies before packing everything into Octave.app. The reason is that
/tmp/dependencies-i386 does not exist on my Mac before building and installing
the sources and so I can make sure that nothing else is packed into Octave.app
that wouldn't be needed.
I hope this helps?
Regards,
Thomas
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
