X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org From: "Jon Beniston" To: Subject: Binary distribution and DLLs Date: Sat, 31 Oct 2009 15:08:04 -0000 Message-ID: <002e01ca5a3b$f1f695c0$d5e3c140$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi, I want to distribute a binary build of some software that I have written, part of which includes some programs that are linked with cygwin1.dll and other Cygwin dlls such as cygexpat-1.dll, cyggmp-3.dll, cygintl-8.dll and so on.=20 Due to some of the other Windows specific components of the software, I don=92t think I can use setup.exe to install the package. My installer can check for the presence of cygwin1.dll and then start Cygwin=92s setup.exe if it doesn=92t exist, but what is the recommended way of dealing with the oth= er dlls? I=92m concerned that in x months time, that cygintl-8.dll will have b= een replaced with cygintl-9.dll, and thus if a user installs the latest packages using setup.exe, they might not get cygintl-8.dll. (My installation appears to only have cygintl-2.dll=A0 cygintl-3.dll=A0 cygintl-8.dll, for example).= =20 Is it safe to include a copy of these dlls (excluding cygwin1.dll) in my programs executable folder (with the source, of course), or will this cause other problems if there is a conflict between two similar dlls? Any thoughts on the best way to deal with this? Cheers, Jon -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple