Am 22.02.2011 09:40, schrieb David Brown: > There is no doubt that it is easier to build a cross-gcc using cygwin > rather than mingw. This is because cygwin has a very thick interface > layer between the programs and the underlying Windows API, so that > cygwin programs see a very Linux-like environment. For example, > programs can use fork, filesystem links, etc., which non-cygwin programs > cannot do on windows. Thus there are also far more Linux-style > utilities for cygwin.
This isn't true. NTFS supports native hard links, for instance, and MinGW just builds the adaption layer into the executables, where Cygwin keeps it separate, and separately upgradable. Of course the results are limited to what the interface layer (MinGW or Cygwin) offers, and MinGW offers fewer features thatn Cygwin does. > There is no doubt that it is easier and faster to /use/ software built > with mingw. This is because mingw does not have the cygwin layer - > programs feel more "native" on windows, and run faster. Well, somewhat. Easier to use depends on which way you want to go. If you have unixy tools like GCC, then feeling more Windows-like isn't a goal. > One of the biggest issues with cygwin is the dreaded cygwin1.dll > problem. Cygwin-generated tools require a number of dlls, and these > come in many different versions. It's not too bad for programs that run > for a bit then stop, but if you've got long-running cygwin programs > (such as an rsync daemon, or a ssh client), it can be a real problem. I have yet to see the "dreaded cygwin1.dll problem" in practice. You may possibly have to add cyggcc* and NLS dlls if you leave NLS enabled, but that's about it. To me, the "dreaded cygwin1.dll problem" is either a myth, or a phantom, or a severely botched installation, and the WASP project stuff for one works well with Cygwin but requires heaps of hacks for MinGW/MSYS builds, and isn't feature complete. So. None of the persons speaking about this "dreaded cygwin1.dll problem" has so far been able to provide me with a reproducible "cygwin1.dll problem" that wasn't in itself an administrative problem, and I have yet to see a situation where I would be required to load two different cygwin1.dll versions at the same time. > And if you want maximum geek points, try a Canadian Cross - use 64-bit > Linux to build a 32-bit mingw-hosted compiler for the 16-bit msp430 :-) I know that WSim is cross-built on Linux, for one - and thus didn't expose libsdl issues (now resolved through use of system-native interfaces), but anyways. -- M. Andree ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
