Mail Archives: cygwin/2004/01/27/15:08:22
On Tue, Jan 27, 2004 at 10:48:16AM -0500, Larry Hall wrote:
>Actually, the recommended approach is to distribute your program that
>depends on Cygwin and then point to cygwin.com's setup to install the
>Cygwin package (and anything else needed/wanted). Obviously, this could
>be automated too.
>
>> This has a slight danger, that the version with your exe might clash with
>>an existing version of cygwin dll already on the computer. To avoid this,
>>you can install your exe and the cygwin dll into a directory of their own.
>>Then you create a file in that directory that has the exact same name as
>>your exe with ".local" appended. This means that when your .exe runs, it
>>will look in the same directory for its dlls before it looks in the windows
>>system dir. That way, your exe gets the version of the dll it expects, but
>>none of the existing software on the machine you install will interact with
>>it. Google for "side-by-side DLLs" if you want to know more.
>
>
>Actually, this will still cause a clash for the Cygwin. But since
>Cygwin DLLs are backward compatible, the recommended approach, which I
>mentioned above, of distributing the Cygwin DLL will avoid any type of
>clash.
Right. You can't have multiple cygwin's operating on the same computer.
Also, lets not forget that any code you link against cygwin will be GPLed
and if you distribute some form of the cygwin DLL you'll need to also
distribute sources of the DLL under the GPL.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -