Re[2]: win32 issues

From: Sinitsyn Valentine (Valentine.Sinitsyn@usu.ru)
Date: Sun Apr 13 2003 - 01:16:16 EDT

Next message: Sinitsyn Valentine: "Re[2]: win32 issues"

Previous message: Michael D. Pritchett: "Re: win32 issues"
In reply to: Kenneth J. Davis: "Re: win32 issues"
Next in thread: Andrew Dunbar: "Re: win32 issues"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

SV>> 1. MinGW port produces two binaries: AbiWord.exe and libAbiWord.dll.
SV>> It is different from MSVC port which produces AbiWord.exe only. This
SV>> causes some difficulties, eg. we need have different nsis scripts for
SV>> these port (or employ some other tricks). May be it is better to link
SV>> AbiWord@MinGW statically?

KJD> Statically would probably be nicer for simplicity, but not really
KJD> necessary. The nsis issue can be fixed by adding /nonfatal
KJD> e.g. File libAbiWord.dll /nonfatal, though this adds a warning for MSVC,
KJD> so a better fix, assuming the MingW defines something, may be
KJD> !ifdef SOMEMINGWDEFINE
KJD> File libAbiWord.dll
KJD> !endif
Ok, I'd prefer to implement static linking, if you don't mind.

Regards,
Valentine

Next message: Sinitsyn Valentine: "Re[2]: win32 issues"
Previous message: Michael D. Pritchett: "Re: win32 issues"
In reply to: Kenneth J. Davis: "Re: win32 issues"
Next in thread: Andrew Dunbar: "Re: win32 issues"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sun Apr 13 2003 - 01:26:21 EDT