FW: FLTK versions in Cygwin [was: Re: units: update, FHS compliance]

Christopher Faylor cgf-use-the-mailinglist-please@cygwin.com
Tue Jan 26 16:26:00 GMT 2010


On Tue, Jan 26, 2010 at 10:14:44AM -0500, Buchbinder, Barry (NIH/NIAID) [E] wrote:
>Christopher Faylor sent the following at Tuesday, January 26, 2010 9:38 AM
>>On Mon, Jan 25, 2010 at 10:28:56PM -0500, Charles Wilson wrote:
>>>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)
>>
>>Cygnus funded the work to provide windows *hosted* cross compilers for
>>other architectures. Targetting *native* targeted win32 did not come
>>until a couple into the life of the project.
>
>references:
>  <http://cygwin.com/cygwin-ug-net/brief-history.html>
>  See '4. "Harnessing the Power of the Internet"' on
><http://www.usenix.org/publications/library/proceedings/usenix-nt98/full_papers/noer/noer_html/noer.html>

Don't know if you're arguing with me or agreeing with me but I actually
helped in the creation of that paper.  I even presented parts of it in
Paris to a bunch of non-English-speaking people at one point.

Unfortunately, the referenced page mixes the term "native" to mean "runs
on windows" vs. "runs without cygwin".  The initial goal of the Cygwin
project was *always* to produce binaries which run in the Cygwin
environment.  The ability to produce objects which didn't rely on Cygwin
came after the project had been around for a couple of years.

cgf

--
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



More information about the Cygwin mailing list