From: Paul G. <pga...@qw...> - 2001-02-10 02:08:18
|
On 9 Feb 2001, at 22:37, the Illustrious rei...@eu... wrote: > On Fri, 09 Feb 2001, Paul Garceau wrote: > > On 9 Feb 2001, at 17:54, the Illustrious > > rei...@eu... wrote: > > > > > I have downloaded the latest package from Cygnus > > > cygwin-1.1.8-2-src.tar.gz. You said "Cygwin", not "Mingw". As Earnie noted on the mailing list, "Mingw" is not "Cygwin". Also, afaik, Mingw does not support symlinks. > > > If I compile and install it, the > > > symbolic links from the include directory to the w32api > > > directory aren't made any longer. I use a self compiled mingw > > > cross compiler and with the new package my windows test > > > programm will not compile any longer (missing w32api > > > includes). I have seen, that the cygnus compiler will add > > > -idirafter /usr/include/w32api to the spec-flie if the win32 > > > option is defined. The mingw compiler doesn't this. > > > > Probably a dumb question, but needs to be asked; are you using > > the -mno-cygwin switch? Since you said above that you had downloaded and are using Cygwin, then you might want to try using this -mno-cygwin switch as well...that is if you want to build Mingw apps under "Cygwin". > No, I have created my own cross compiler from the sources. > I have configured the compiler to be a mingw compiler, not a > cygwin compiler, therfore I don't need the no-cygwin switch. "Cygwin" requires -mno-cygwin to do mingw compiles. GCC from Cygwin is not the same GCC from Mingw. They are different. Cygwin gcc needs cygwin.dll to work, mingw does not. > The > problem is, that the spec file for the compiler is missing the > path to the new w32api directory. As noted on the mailing list, this is not a Mingw concern...it is a Cygwin concern. You might want to mention it on the cygwin mailing list if you still have any doubt about what people are telling you... > > > > > I haven't been able to download the latest cygwin release to > > test this. Even so, again, this is probably something you > > already know, it is my impression that if you select -mno- > > cygwin, you automatically include the win32api. At least that > > was how I understood the latest changes to cygwin that were > > made re: win32api whenver -mno-cygwin was invoked. In other > > words you shouldn't have to specifically define "including" the > > win32api in any way shape or form, it is assumed that if you > > use -mno-cygwin then that automatically invokes the inclusion > > of the win32api headers. > Thats also right, if it is a cygwin compiler. Then the spec file > has an entry for w32api and mingw. But I have a mingw compiler > ... see above. *ahem*...you can not have a Mingw compiler if you are using Cygwin. You _can_ use Mingw runtime headers, which is what the - mno-cygwin switch is there for. It is also the reason why the Cygwin distribution includes a directory for Mingw (see usr/include/ under Cygwin). > > I have to add a line to the spec file of the compiler. Yes, for a Cygwin compiler, you do. Peace, Paul G. > > Thank you for your input > Regards, > Reinhard > > -- > Ing. Reinhard Jessich mailto: > rei...@eu... A-1190 Vienna, Goergengasse 2/2/1 > phone: +43/1/3692600 http://members.eunet.at/jessich mobile: > +43/664/1735439 > Nothing real can be threatened. Nothing unreal exists. |