Re: mkoctfile in Octave for Windows cannot find liboctave and other Octave-standard libraries

[Tatsuro MATSUOKA]

Hello

Perhaps for your case,

export OCTLIBDIR=/f/Octave4Windows/Octave/octave-3.4.3/lib/octave/3.4.3

The correction will be required if the sub folder structure is different from 
the above example. 

Regards

Tatsuro
--- On Fri, 2012/2/24, Tatsuro MATSUOKA wrote:

> Hello
> 
> Set environment variable OCTLIBDIR changes values of OCTLIBDIR in the 
> mkoctfile. 
> 
> $ export OCTLIBDIR=(folder name suitable your setting)
> 
> Regards
> 
> Tatsuro
> 
> --- On Fri, 2012/2/24, E. Joshua Rigler  wrote:
> 
> > Tatsuro,
> > 
> > As per your request:
> > 
> > $ mkoctfile.exe -p PCTLIBDIR
> > /c/OctaveB/octave-3.4.3/lib/octave/3.4.3
> > 
> > So, no this does not match my install folder structure. My install
> > folder is /f/Octave4Windows, where 'f' is an external hard drive.
> > 
> > FWIW, I was eventually able to compile my mex functions by explicitly
> > passing the library path via -L options to mkoctfile.exe. This seems
> > less than ideal though. Is there a way to force mkoctfile.exe to
> > respect my installation directory structure?
> > 
> > -EJR
> > 
> > 
> > On Thu, Feb 23, 2012 at 4:32 PM, Tatsuro MATSUOKA <address@hidden> wrote:
> > > Hello
> > >
> > > Please execute
> > >
> > > $ mkoctfile -p OCTLIBDIR
> > >
> > > Does the result match to your install folder structure?
> > >
> > > Regards
> > >
> > > Tatsuro
> > >
> > >
> > > --- On Fri, 2012/2/24, E. Joshua Rigler <address@hidden> wrote:
> > >
> > >> I am attempting to compile mex files using the command-line mkoctfile
> > >> from the MINGW32 version of Octave for Windows. I get the following
> > >> errors:
> > >>
> > >> $ mkoctfile.exe -mex fits_read_image.c
> > >> -L/f/Octave4Windows/Octave3.4.3_gcc4.5.2/lib -lcfitsio
> > >> -I/f/Octave4Windows/Octave3.4.3_gcc4.5.2/include/octave-3.4.3/octave
> > >> -I/f/Octave4Windows/Octave3.4.3_gcc4.5.2/include
> > >> f:/octave4windows/octave3.4.3_gcc4.5.2/mingw32/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe:
> > >> cannot find -loctinterp
> > >> f:/octave4windows/octave3.4.3_gcc4.5.2/mingw32/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe:
> > >> cannot find -loctave
> > >> f:/octave4windows/octave3.4.3_gcc4.5.2/mingw32/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe:
> > >> cannot find -lcruft
> > >> collect2: ld returned 1 exit status
> > >>
> > >> Note 1: I am doing this after calling msys.bat, and mounting the
> > >> mingw32 directory as /mingw
> > >> Note 2: manually specifying the path for the libcfitsio.a library
> > >> seems to make ld.exe happy. It is what I would consider the Octave
> > >> standard libraries (i.e., liboctinterp, liboctave, libcruft) that
> > >> ld.exe cannot find when called from mkoctfile. What's worse, this
> > >> mkoctfile.exe file is some kind of binary file, not a script like I am
> > >> accustomed to, so I can't even read it to see what is happening.
> > >>
> > >> Any help would be appreciated, or just confirmation that it is
> > >> currently impossible to compile mex files in Octave for Windows so I
> > >> can stop wasting my time.
> > >>
> > >> -EJR
> > >> _______________________________________________
> > >> Help-octave mailing list
> > >> address@hidden
> > >> https://mailman.cae.wisc.edu/listinfo/help-octave
> > >>
> > 
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://mailman.cae.wisc.edu/listinfo/help-octave
>