X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4B5E6178.40709@cwilson.fastmail.fm> Date: Mon, 25 Jan 2010 22:28:56 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 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> <4B5D7921 DOT 6060004 AT go4more DOT de> <4B5DE824 DOT 6030802 AT users DOT sourceforge DOT net> In-Reply-To: <4B5DE824.6030802@users.sourceforge.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 Note-from-DJ: This may be spam Yaakov (Cygwin/X) wrote: > On 25/01/2010 04:57, Albrecht Schlosser wrote: >> 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. > > Since when are matters such as this decided by opinion polls? I bet > most of the voters didn't use Cygwin or even know what it is. Did you > have a poll to decide how FLTK should be built on Linux? Didn't think > so. I am NOT impressed. Meh. Unlike linux, there is a significant portion of the cygwin user base that treats cygwin simply as a "build environment" -- but use a compiler for native win32 $hosts. I don't much like it, but that's reality. (...why did Cygnus fund the early development, in the first place? To have a windows-hosted build environment for xxx-target compilers: in this case, xxx = native-win32) So, the FLTK development and user community thinks of Cygwin that way, by a 3-to-1 majority. Maybe we ought to try to convince them to treat cygwin as a full-class platform, rather than as an afterthought to native win32 support? I suspect a better approach to that end is more honey, less vinegar. I know, I know -- that's pretty rich, coming from me. But...there it is. > Like any other platform, the only people that should have a say in any > package's behaviour on Cygwin are the Cygwin managers and maintainers. > We have made Cygwin a *NIX/X11 platform, and we have decided that gcc > will not support -mno-cygwin (which was broken anyway). *That* is the > ONLY opinion that should matter in this discussion. Well, by removing -mno-cygwin, we've more or less assured that this will happen eventually. People are going to get tired of being stuck with 'gcc-3 -mno-cygwin' eventually, and are going to want to use i686-mingw32-gcc(4) at some point. Then, they'll have to switch over to an actual cross-compile configury for their cygwin-hosted native builds. But that'll take a while. > Unfortunately this attitude is by no means limited to FLTK, and any > frustration with this topic is based more on the frequency of this sort > of thinking than with FLTK in particular. Yep, but...that's the nature of (our) beast. -- Chuck -- 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