Michael Goffioul wrote:
> 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}"
> ...
>
>
I think you're probably the only Octave developer who understands the
mechanics of this. Maybe you could help out Benjamin?
D.
--
David Bateman [EMAIL PROTECTED]
Motorola Labs - Paris +33 1 69 35 48 04 (Ph)
Parc Les Algorithmes, Commune de St Aubin +33 6 72 01 06 33 (Mob)
91193 Gif-Sur-Yvette FRANCE +33 1 69 35 77 01 (Fax)
The information contained in this communication has been classified as:
[x] General Business Information
[ ] Motorola Internal Use Only
[ ] Motorola Confidential Proprietary
-------------------------------------------------------------------------
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
