Message-ID: <499EBFF0.4010307@gmail.com>
Date: Fri, 20 Feb 2009 14:36:32 +0000
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Windows Mobile?
References: <2638D07BD46A48F6A2EFD3165EA6130B@luggage> <a1643f9bfacebd711fd8699980b3bb63@mail.smartmobili.com> <499EB6DD.1080305@gmail.com> <0ef59f26ed0ef91d93beae42b7871fa3@mail.smartmobili.com>
In-Reply-To: <0ef59f26ed0ef91d93beae42b7871fa3@mail.smartmobili.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Vincent R. wrote:

> Still don't understand because cegcc provides you with POSIX API!

  Oh, wow!  I didn't know that, I thought it was more like MinGW; it's
actually far more comprehensive than I thought.

> And what would mean to port cygwin on Windows Mobile, does it mean you want
> a terminal with a compiler running directly on the device ?

  You'll have to ask Harold, but I was acting under the assumption that that
is what he wanted, or at any rate, a version of cygwin1.dll that runs on CE.

> You need to know that cegcc is actually a common name for two different
> toolchains
> 
> cegcc = POSIX API + newlib libc
> mingw32ce = mingw for wince : native API + native libc
> 
> To say it differently :
> cegcc = cygwin for wince
> mingw32ce = mingw for wince
> 
> But maybe I am the one missing something ?

  No, I was; thank you for explaining.  I haven't been paying attention to the
windows mobile platforms (until just the other day as it happens, when I was
trying to find out if anyone still uses sh-*-pe, which I gather you guys don't).

    cheers,
      DaveK

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/