On Sat, Apr 15, 2006 at 05:02:09PM +0200, Abdelrazak Younes wrote: > Enrico Forestieri a écrit :
> > I mean that you know that you should use -mno-cygwin only after > > ascertaining that you want windows packaging. Until this point, > > the configure script has already performed many checks using > > the cygwin compiler and thus it has made many wrong choices. > > I cannot even have the Qt library recognized because the previous > > choices bring in options that make the check for it fail. > > > > So, this is not the way to go and instead you have to specify > > the CC, CXX, CPP, CXXCPP variables when invoking configure, > > such that the right compiler is used from the beginning. > > It's weird because it works here. I mean I see the -mno-cygwin. But I > don't know if it comes from the new cygwin.m4 or the > --windows-packaging. The difference here is that cygwin gcc is not > installed on my system so all the tests are done with mngw gcc (which > doesn't mind the -mno-cygwin option apparently). That explains it, then. I can assure you that it doesn't work with the cygwin compiler. > > I am sorry, it doesn't work. The only thing which works is > > automatically adding -DQ_CYGWIN_WIN to CPPFLAGS when it is > > needed. Working cygwin.m4 attached. > > OK, I will commit that. Thanks a lot, Abdel. > > Anyway, I don't think that it is a so great pain having to specify > > some variables on the configure command line. You can setup a script > > for that if you don't want type them everytime. > > It's not about me Enrico, it's about the casual tester. But I agree it's > not a big deal. Oh... But it should be clear for the casual user that he must not use cygwin to build a native version of LyX because that's unsupported. -- Enrico
