Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: Chris Faylor Date: Mon, 16 Oct 2000 18:15:04 -0400 To: cygwin AT sources DOT redhat DOT com Cc: jfpatry AT sunspirestudios DOT com, support AT sunspirestudios DOT com Subject: Re: distribution suggestion Message-ID: <20001016181504.A15694@cygnus.com> Reply-To: cygwin AT sources DOT redhat DOT com Mail-Followup-To: cygwin AT sources DOT redhat DOT com, jfpatry AT sunspirestudios DOT com, support AT sunspirestudios DOT com References: <003201c03752$74404970$f7c723cb AT lifelesswks> <20001016141212 DOT A5544 AT cgl DOT uwaterloo DOT ca> <018201c037ba$6eb62750$f7c723cb AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <018201c037ba$6eb62750$f7c723cb@lifelesswks>; from robert.collins@itdomain.com.au on Tue, Oct 17, 2000 at 08:45:30AM +1100 On Tue, Oct 17, 2000 at 08:45:30AM +1100, Robert Collins wrote: >Jasmin, >I've cc'd my reply to the cygwin mailing list as I cannot give you a full >answer (and I don't _recall_ seeing any mailing items that match to this on >the list to date). > >Cygwiners: There's a neat little game "tuxracer" >http://tuxracer.sourceforge.net . When I looked at it I found it uses >cygwin1.dll & glut.. however they distibute cygwin1.dll (which gives rise to >our favourite conflict). > >I suggested packaging cygwin1.dll separately as the runtime will run against >newer cygwin1.dll's, and users who need it can download it, but this >obviously needs user knowledge of whats going on :-]--- > >Is there a good answer to Jasmin's question below? Renaming cygwin1.dll should have no effect. As always, the answer is to just use the most recent version of cygwin1.dll. It's a no brainer. However, I hope that, if they are distributing cygwin, they are in compliance with the GPL. I assume that since there are conflicts they are probably releasing B20.1 or something. That means that they should, as a minimum, be providing all of the sources that went into building B20.1 cygwin. I don't see any reason why an executable compiled with -mno-cygwin would fail to run on W2K. I think the best solution is to use -mno-cygwin and figure out why it doesn't run on W2K. cgf >----- Original Message ----- >From: "Jasmin Patry" >To: "Robert Collins" >Cc: >Sent: Tuesday, October 17, 2000 5:12 AM >Subject: Re: distribution suggestion > > >> On Mon, Oct 16, 2000 at 08:21:22PM +1100, Robert Collins wrote: >> > Hi, >> > I notice you use cygwin1.dll as a support library for tuxracer. >> > >> > All windows users that have cygwin1.dll in memory will find tuxracer >doesn't >> > work, or stackdumps unless their copy of cygwin1.dll is the same build >as >> > yours. The solution is to move or rename the cygwin1.dll from your >> > distribution. >> >> Thanks a lot for pointing this out. We'd prefer to use mingw32 to >> compile Tux Racer (hence no cygwin1.dll), but unfortunately the >> resulting executable doesn't run under Windows 2000. >> >> Do you know if renaming cygwin1.dll to something else will work (after >> re-linking tuxracer against that new dll, of course)? Or will it still >> try to use the same shared memory segments as before, resulting in the >> same problem? >> >> Thanks, >> Jasmin >> >> -- >> Jasmin Patry Lead Programmer, Tux Racer >> jfpatry AT sunspirestudios DOT com http://www.tuxracer.com >> > > >-- >Want to unsubscribe from this list? >Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com -- cgf AT cygnus DOT com Cygnus Solutions, a Red Hat company http://sourceware.cygnus.com/ http://www.redhat.com/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com