[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [mxe-octave] differences in components between official build and se
From: |
Tatsuro MATSUOKA |
Subject: |
Re: [mxe-octave] differences in components between official build and self build |
Date: |
Fri, 29 Jul 2016 10:06:39 +0900 (JST) |
----- Original Message -----
> From: John W. Eaton <address@hidden>
> To: Tatsuro MATSUOKA <address@hidden>; "address@hidden" <address@hidden>
> Cc: address@hidden
> Date: 2016/7/27, Wed 21:58
> Subject: Re: [mxe-octave] differences in components between official build
> and self build
>
> On 07/27/2016 02:45 AM, Tatsuro MATSUOKA wrote:
>> The package of ocgtave-4.0.3 for windows on official site
>> includes
>>
>> 1. pre-built octave-forge packages.
>> 2. Qt tools , moc.exe. uic.exe etcs.
>>
>> At least above two does not included in self build packages by mxe on
> linux.
>>
>> Consulting wiki for mxe cross build of octave for windows on unix,
>> (http://wiki.octave.org/Windows_Installer)
>> I cannot find any description on this matter.
>>
>> 1. is not matter because we can build octave-forge package by
> build_packages.m
>>
>> However, 2. is a problem when I want to build octave on native windows
> using the octave package.
>>
>> Perhaps I have to modify src/qt.mk on mxe-octave.
>>
>> If possible, please give me a hint.
>
> They are both options for the mxe-octave configure script:
>
> ./configure --help
>
> [...]
>
> --enable-binary-packages
> Enable creating binary Octave Forge packages
> --enable-devel-tools Enable creating developer tools such as gdb
>
>
> jwe
Thanks! I could include octave-forge packages and developer tools in
the octave installer for windows (64 bit) using mxe-octave.
Tatsuro