--- David Bateman ha scritto:
> 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
while for cygwin is cygcruft.dll
that caused me some headache on the
octave-3.0.x porting.
> > - MSVC uses <name>.lib import files, MinGW uses
> lib<name>.a import files
for cygwin lib<name>.a
> > - ...
> >
> > 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.
>
I suspect it is time to separate Mingw and cygwin
configuration, and I am afraid I should work on it.
Marco Atzeri
cygwin-octave maintainer
Hai un indirizzo email difficile da ricordare?
Scegli quello che hai sempre desiderato su Yahoo! Mail
http://it.docs.yahoo.com/nuovo_indirizzo.html
-------------------------------------------------------------------------
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
