On 07/07/2009 12:12, Alexander Neundorf wrote: > I would suggest you try to get them first into cmake, and from there will will > automatically flow into cygwin cmake.
I'm not the Cygwin cmake package maintainer, so I would prefer to work with/through him rather than springing such a change on him via upstream without notice. > That doesn't sound like a good idea, since it still is WIN32, and all > documentation and postings on the mailing list will say that it has WIN32. > So, please don't remove that. I'm talking about the CMake WIN32 define, not the CPP #define. Either way, neither should be on for Cygwin (as is the default for gcc), since Cygwin is a *NIX/X11 platform which has almost nothing in common with WIN32. Having built a number of packages with CMake, both in and out of KDE, I can tell you that grouping CYGWIN and WIN32 together is almost always wrong. So yes, I do intend to pursue removing the WIN32 CMake define for Cygwin. Yaakov Cygwin Ports _______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
