How to port uclibc to Windows CE

[Steve Bennett]

On 09/02/2011, at 7:45 AM, Philip Nye wrote:

> On 08/02/2011 19:33, David Lynch Jr. wrote:
> ...
>> 	If you are looking to port an existing *nix application to windows that
>> makes heavy use of less common API's you are looking at an enormous
>> amount of work.
>> 	But if you are trying to develop applications that you expect to build
>> and work on many platforms, and you have control over the coding
>> standards, portability is not that hard to achieve.
> 
> This does depend very much on what sort of thing your program does and which sort of library calls it uses. For programs of some types I'm sure you're right, In other areas it's a nightmare. taowei said nothing about his applications, or what his WinCE platform was.
> 
> I've been writing network stuff that relies heavily on lots of different multicast groups and sockets and even porting from Linux to BSD to OSX is a headache, let alone to Windows - and once in Windows, you get the same trouble from Win 2000 to WinXP to Win7.

I have been unfortunate enough to work on a WinCE-based project.
It was a nightmare from beginning to end.
Not only is WinCE not Unix, POSIX or anything else sane, it also isn't "Win32".
Many of the Win32 APIs are missing or behave differently on WinCE.
Especially all the necessary ones such as a filesystem access and network interfaces.

And don't get me started on using Visual Studio as a build environment!

No, long before you consider porting uClibc to WinCE, you should consider
redesigning the entire project or getting a new job.

Cheers,
Steve

--
µWeb: Embedded Web Framework - http://uweb.workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au      P: 0434 921 300
E: steveb at workware.net.au   F: 07 3102 9221