From: Earnie B. <ea...@us...> - 2006-11-10 02:03:55
|
Quoting John Pye <joh...@st...>: > > Perhaps someone knows somewhere on the net where all this is clearly > explained? > There is nothing as clear as the source itself. If you're willing to sniff through the source and ask intelligent questions then you'll get intelligent answers. MSYS is nothing more than an older version of Cygwin with changes that I made based on issues users were having using Cygwin with native programs and my desire to provide MinGW with a shell environment that was capable of executing configure. I removed the dependencies on the windows registry for the file system mapping and removed most of the ability of symlink emulation relying on changes to ln to copy rather than create a symlink. Programs that use the native runtime dll will never be able to resolve the Cygwin or MSYS mappings but there are methods provided by either DLL that can help. These API were mostly meant to be friendly API for the creation of Cygwin tools and never really meant to be used beyond Cygwin or MSYS itself but it is possible to use them. Earnie Boyd -- Please post responsibly: * Use text posts instead of html; many list members just trash mail with html. * Do not use multipart mime to send both text and html versions. * Do not top post replies; post inline with the parts you are responding to. * Trim the post replies; remove irrelevant information from the quoted article. * Original posters: ** Provide small complete examples of the problem. ** Provide the full command that produced errors. ** Provide the versions of the software used. -- ****************************************************************************** * The user of this server has agreed to allow the use of a trailer in the * * mail that he sends for advertising purposes. This advertisment is added * * by the server and is not in the control of the user of our services. * ****************************************************************************** Easy Blogger Creator: <a href="http://give-me-an-offer.com/1006/">Offer 1006</a> 4 Seasons Wine - Buy 6, Get 6 Free <a href="http://give-me-an-offer.com/1007/">Offer 1007</a> |
From: Brian D. <br...@de...> - 2006-11-11 20:36:18
|
Earnie Boyd wrote: > > But msvcrt.dll is part of the operating system. > > > > That truth doesn't invalidate my statement. Actually, I might have > mis-spoke here in that Cygwin uses MSVCRT.DLL but it does use other DLL > libraries so we will continue with that example. Using your statement > I can say that cygwin.dll is part of the Cygwin OS. An operating > system is nothing more than processes someone wrote as source code > controlling the use of the equipment. Using a library as an add on > enhancement if it exists doesn't create an infection just as using an > executable doesn't infect my program. The key here is that the program > must function without the library or i.e. not be dependent on it to > function. Once the program has a dependency on the GPL library to > function properly then it becomes infected by the GPL. I think he was referring to the clause in paragraph 3 that says: > However, as a > special exception, the source code distributed need not include > anything that is normally distributed (in either source or binary > form) with the major components (compiler, kernel, and so on) of the > operating system on which the executable runs, unless that component > itself accompanies the executable. So, in this case, if a GPL program links (either normal linking or runtime linking with LoadLibrary) to non-GPL libraries that are part of the system, then the author need not provice source for those libraries. If this were not the case it would be virtually impossible to distribute a GPL binary of anything under windows as even the most trivial of programs links against one or more of -luser32 -lkernel32 -ladvapi32 (or failing that -lntoskrnl). Brian |