How to port uclibc to Windows CE

[David Lynch Jr.]

	I am not specifically familiar with Windows CE. But I have done lots of
cross platform work with windows.  Ignoring tangents like the Windows
Posix subsystem and Cygwin, normal windows - microsoft's C libraries
provides a significant portion of POSIX support.  The critical problem
is that windows developers almost univerally use the Windows specific
API's over the more portable POSIX API's. 
	In general it is not very hard to write code that will compile and run
on both windows and *nix. The hard part is keeping software developers
from using CreateFile() rather than the more portable fopen() and other
similar choices when there is no good reason for selecting the Windows
specific API over the portable one. 
	I have managed two major product suites that had to work cross platform
(Windows, Linux, OpenBSD, OSX), that had numerous applications,
services, even device drivers, and the only hard part was keeping the
windows developers from running amuk. 
	Neither porting uClibc to windows nor approaches like Cygwin resolve
that.  



-- 
Dave Lynch                                                  DLA Systems
Software Development:                                    Embedded Linux
717.587.7774           dhlii at dlasys.net    http://www.dlasys.net
Over 25 years' experience in platforms, languages, and technologies too
numerous to list.

"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction."
Albert Einstein


On Tue, 2011-02-08 at 09:50 +0000, Philip Nye wrote:
> On 08/02/2011 08:50, Rob Landley wrote:
> > On 02/08/2011 01:43 AM, taowei wrote:
> >> Hello, everyone:
> >> I'm a newer for uclibc. I have two questions about uclibc and I look
> forward to your reply. Thank you very much.
> >> Question1: Is uclibccompatible with POSIX?
> >
> > Reasonably, yes.  Still catching up with Posix 2008 in places.
> >
> >> Question2: uclibc supports embedded linux. I want to port it to Windows CE,
> >
> > Why?
> >
> >> but I don't know how to do it. Can you give me some advices on it?
> >
> > Not really.  It makes about as much sense to me as rewriting it in
> > cobol, but it's your life...
> 
> As a follow-up to Rob's succinct analysis, there is obviously motivation for 
> supporting POSIX applications - and therefore all the associated C-library 
> calls - on Windows platforms, however uClibc is probably not what you want. 
> You'd be better looking into Cygwin and/or MinGW, but I've little idea of 
> the state of them on WinCE.
> 
> Philip
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://lists.busybox.net/mailman/listinfo/uclibc