octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mkoctfile does not find octave/oct.h in MXE-Octave 3.8.1-5 (Windows


From: Tatsuro MATSUOKA
Subject: Re: mkoctfile does not find octave/oct.h in MXE-Octave 3.8.1-5 (Windows 7, 32 bits)
Date: Fri, 25 Jul 2014 16:21:03 +0900 (JST)

> From: Julien Bect 

> To: Tatsuro MATSUOKA 
> Cc: Octave Maintainers 
> Date: 2014/7/25, Fri 15:23
> Subject: Re: mkoctfile does not find octave/oct.h in MXE-Octave 3.8.1-5 
> (Windows 7, 32 bits)
> 
> Le 24/07/2014 14:10, Julien Bect a écrit :
>>  Here is what I get from a terminal :
>> 
>>  $ mkoctfile -p LIBDIR
>>  \root\mxe-octave\usr\i686-w64-mingw32\lib
>>  $ mkoctfile -p INCLUDEDIR
>>  \root\mxe-octave\usr\i686-w64-mingw32\include
>>  $ mkoctfile -p OCTINCLUDEDIR
>> 
> \root\mxe-octave\usr\i686-w64-mingw32\include\octave-3.8.1\octave
>> 
>>  And here is what I get from Octave :
>> 
>>  >> mkoctfile -p LIBDIR
>>  C:\Octave\Octave-3.8.1\lib
>>  >> mkoctfile -p INCLUDEDIR
>>  C:\Octave\Octave-3.8.1\include
>>  >> mkoctfile -p OCTINCLUDEDIR
>>  C:\Octave\Octave-3.8.1\include\octave-3.8.1\octave
>> 
>>  My include path problem is thus solved if I build from Octave...
> 
> Is this the expected behaviour ?
> 
> Or should I file a bug report for this difference between the command 
> line behaviour and the inside-Octave behaviour of mkoctfile ?


From the source of mkoctfile, it is the expected behavior.
If you would like to mkoctfile from terminal, please try the below before you 
use mkoctfile

$ export LIBDIR=/c/Octave/Octave-3.8.1/lib
$ export INCLUDEDIR=/c/Octave/Octave-3.8.1/include
$ export OCTINCLUDEDIR=/c/Octave/Octave-3.8.1/include/octave-3.8.1/octave

Tatsuro



reply via email to

[Prev in Thread] Current Thread [Next in Thread]