X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B5D7921.6060004@go4more.de> Date: Mon, 25 Jan 2010 11:57:37 +0100 From: Albrecht Schlosser User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: FLTK versions in Cygwin [was: Re: units: update, FHS compliance] References: <657633 DOT 34813 DOT qm AT web25501 DOT mail DOT ukl DOT yahoo DOT com> <4B5B16A5 DOT 4080104 AT go4more DOT de> <4B5BAEC3 DOT 1050507 AT users DOT sourceforge DOT net> <4B5C60A0 DOT 4050106 AT go4more DOT de> <4B5C9702 DOT 3060908 AT users DOT sourceforge DOT net> <4B5CDF1E DOT 2010107 AT go4more DOT de> <4B5CF76F DOT 5070308 AT users DOT sourceforge DOT net> In-Reply-To: <4B5CF76F.5070308@users.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 Yaakov (Cygwin/X) wrote: > On 24/01/2010 18:00, Albrecht Schlosser wrote: >> I'am aware that -mno-cygwin is no longer supported, but there's >> nothing we can do until a working gcc-4 cross compiler exists. >> So long we need to use gcc-3 for Windows/GDI builds (or Cygwin). > > That's what I'm trying to tell you: -mno-cygwin mean(t) just that: NO > cygwin. I knew that. Thanks nevertheless. > It shouldn't be the default on Cygwin to not build for Cygwin; > after all, you wouldn't have the default on Linux to cross-compile to > Win32, would you? If you want to provide the cross-compiling option, > that's fine, but it should be an *option*, not the default. Point taken. But unfortunately the FLTK community decided it the other way with a majority of 74% (this must have been in or before 2003): http://www.fltk.org/poll.php?r1 Thus this is not likely to be changed. Sorry. From a Cygwin point of view you're right, of course, and I wouldn't have any problems with this change. However, some (many?) developers (including me) use Cygwin as a development platform to create native Windows programs w/o the need to use the cygwin1.dll. The occasional user (developer) who tries to configure a project (FLTK) would probably be surprised if he created .exe files that can't be run on another PC (w/o a Cygwin installation). If s/he needs the Cygwin POSIX environment, s/he should know what to do and use --enable-cygwin explicitly. YMMV. BTW.: I appreciate all the good work for Cygwin and I don't want to miss it anymore as a development platform. And before you say "use MinGW": I have it installed, too, but I prefer Cygwin. [concerning not installing *.dll.a file] >> Yep, that's what I expected, but didn't check (yet). This may >> well be changed... > > It should be, although the workaround is easy in the meantime. I'll take a look into it and keep you informed. Albrecht -- 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