On Thu, Apr 13, 2006 at 12:43:56PM +0000, Angus Leeming wrote: > A question for you: If I were to fo the -mno-cygwin route and build LyX using > the Cygwin environment, then I'll also have to continue to build the external > libraries that LyX links against (aspell, iconv, gettext). Ie, I won't be able > to use the equivalent libraries packaged by Cygwin will I?
Exactly. Even if you have all the cygwin libs, they are not seen when you use -mno-cygwin, and the includes also are searched in different paths as "gcc -print-search-dirs" and "gcc -mno-cygwin -print-search-dirs" demonstrate. So a pollution is unlikely to happen and I have never seen it except in a single case with "#include <float.h>", but this is a very peculiar case due to an "#include_next<float.h>" in the mingw float.h. After examining the search path used by the compiler, I solved it with a well placed symlink. The only mingw lib you count on in cygwin is libz. You have to compile by yourself everything else you need. As regards LyX, I only need compiling libiconv, aspell and Qt. The -mno-cygwin is supported in cygwin for the only purpose of compiling their installation tool (setup.exe) which, for obvious reasons, cannot depend on the cygwin dll. So, the mingw support is limited in cygwin but it is not going to disappear. -- Enrico
