From: Wayne Davison (wayned@users.sourceforge.net)
Date: Fri Oct 06 2000 - 18:52:51 EDT
On Fri, 6 Oct 2000, Timothee Besset wrote:
> One question though: what's the purpose of the Makefile.mygwin? The
> configure script works fine with cygwin already?
That's "mingw", not "mygwin". See http://www.mingw.org/ for full details,
but in a nutshell: it's how you can use the gnu tools to compile Win32
applications without all the posix-layer stuff that Cygwin provides. This
means that we can't depend on being able to run the configure script
(since there's no guarantee that /bin/sh even exists), and the Makefile
actually creates a DLL (which the existing Makefile does not attempt).
Also, mingw appears to be better licensed than Cygwin, so you can use it
to create a DLL that doesn't transmogrify your software's license into the
GPL. For instance, if someone were to use Cygwin to release a libxml.dll,
you would have to distribute a cygwin*.dll to use it, and that would
encumber the libxml library with the GPL's restrictions (not the LGPL that
it currently uses). I believe at that point it would be impossible to use
such a libxml.dll with any non-GPLed code (BSD, Artistic, or whatever)
without it too becoming GPLed.
So, Makefile.mingw sets up the mingw build environment to create a
regular, (LGPLed) Win32 DLL of libxml -- one that should be able to be
used by normal Win32 applications.
..wayne..
---- Message from the list xml@rpmfind.net Archived at : http://xmlsoft.org/messages/ to unsubscribe: echo "unsubscribe xml" | mail majordomo@rpmfind.net
This archive was generated by hypermail 2b29 : Fri Oct 06 2000 - 19:43:21 EDT