On Fri, Jun 27, 2008 at 12:24 PM, David Bateman
<[EMAIL PROTECTED]> wrote:
> How easy would it be to adapt you NSI script to the MinGW package? I
> also think it would be a good idea to wrap the compilers and the option
> to install them in the installer as this is where the MinGW installer
> will excel relative to the MSVC installer.
>
> Basically I know nothing above the NSI scripting language and avoided
> learning it, but it seems that the MSVC and MinGW packages will be so
> similar that the modifications in NSI for one or the other will be minimal.
Although the file structure would probably be very similar, you might
be annoyed by tiny details, like for instance file naming convention:
- MSVC uses cruft.dll, MinGW uses libcruft.dll
- MSVC uses <name>.lib import files, MinGW uses lib<name>.a import files
- ...
All these differences have to be identified and put into some macro
to be able to use the same .nsi file from MSVC and MinGW. For instance
to address the import lib filename, you can use something like
(@...@ symbols are replaced at run-time, through sed)
!define IMPLIB_PRE @IMPLIB_PRE@
!define IMPLIB_EXT @IMPLIB_EXT@
...
File "${ROOT}/lib/${IMPLIB_PRE}zlib.${IMPLIB_EXT}"
...
Michael.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
