X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SARE_SUB_ENC_UTF8 X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Fri, 20 Feb 2009 15:17:33 +0100 From: "Vincent R." To: cygwin AT cygwin DOT com Subject: Re: Windows =?UTF-8?Q?Mobile=3F?= In-Reply-To: <499EB6DD.1080305@gmail.com> References: <2638D07BD46A48F6A2EFD3165EA6130B AT luggage> <499EB6DD DOT 1080305 AT gmail DOT com> Message-ID: <0ef59f26ed0ef91d93beae42b7871fa3@mail.smartmobili.com> X-Sender: forumer AT smartmobili DOT com User-Agent: RoundCube Webmail/0.2 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Fri, 20 Feb 2009 13:57:49 +0000, Dave Korn wrote: > Vincent R. wrote: >> On Fri, 20 Feb 2009 11:20:41 -0000, "Harold Fuchs" wrote: >>> Are there any plans to port Cygwin to Windows Mobile? Dates? > > Not that I know of. > >>> If not, I'd be interested to know why. > > Well, the reason I wasn't planning to do it is because I don't ever use > Windows Mobile. I can't speak for anyone else of course. > >> You can already use cegcc, don't see the point to port cygwin. > > Huh? You can already use MinGW on ordinary windows, but there was a > point > in writing Cygwin in the first place. Neither cegcc nor MinGW give you a > Posix API and environment; that's what Cygwin does on non-mobile Windows, > and > that's what would be the point of porting it to Mobile Windows. Am I > missing > something here? > Still don't understand because cegcc provides you with POSIX API! 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 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 ? -- 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/