(sorry mosfet, did not check well the "To:" adress filled by gmail :( )

from cegcc web site:

What's the meaning of *arm-cegcc* and *arm-mingw32ce* ? They both describe
the target platform : we're building for an *ARM* processor, running the
Windows CE operating system, on unknown hardware (could be any brand of PDA
or smart phone). In the *cegcc* case, there's a portability layer; in the *
mingw32ce* case there isn't.

so basically cegcc is a newlib port that does this portability layer job.

But Vincent wants a native job. So the better is to contact this lib's
maintainers I think.

2008/11/6 mosfet <[EMAIL PROTECTED]>


>
> -------- Original Message --------
> Subject: Re: [Cegcc-devel] question about what to do for the libpng port
> Date: Thu, 06 Nov 2008 14:02:00 +0100
> From: mosfet <[EMAIL PROTECTED]>
> To: Vincent Torri <[EMAIL PROTECTED]>
>
> On Thu, 6 Nov 2008 12:12:07 +0100 (CET), Vincent Torri
> <[EMAIL PROTECTED]> wrote:
> >>> the best way would be libpng to add 2 functions to open and close a
> >>> file,
> >>
> >>> so that we can manage all the platform in a portable manner :)
> >>
> >> I agree with this last solution...
> >> But I don't understand the issue here because I thought cegcc implements
> >> all posix functions so why do you need to
> >> use CreateFile and not open or fopen ?
> >
> > my aim is to compile only with mingw32ce, and not cegcc. I plan to
> provide
> > only native ports, like I did for zlib, libjpeg and freetype.
> >
> > Vincent
> >
>
> Um I understand. That's why the last time I did this kind of port I have
> developped a posix emulation
> layer.
> I have implemented all posix functions, getenv, open, create, .... with
> file api based on fopen because from a FILE* it's possible
> to get the underlying file descriptor (bot not the opposite) and I was
> maintening an array mapping filedescriptor and FILE*.
> Now I know that usually open source project on windows CE use HANDLE as a
> filedescriptor.
> Unfortunately this year I was supposed to finish a dll implementing all
> this posix functions and include it
> in the software we provide to HTC. It would have allowed to close all this
> issues about missing posix functions.
>
> But I still think that you should email linpng, zlib , ... mainteners to
> tell them that if they plan to release a new version
> they should replace all posix functions by what you suggest (a wrapper that
> could be then implemented using OS specific).
>
> Vincent, I suppose you don't have time to do it but what about creating a
> project let's call it posix4ce
> that would implement a DLL with posix functions it would help projects to
> access windows ce device more easily.
> This is something I am dreaming for about 4 years and I think it's
> something I have mentioned in my first post on this ML.
> To finish with this subject, when I look at open source projects, I can see
> that each one is always reimplementing the same
> thing and I find it fucking stupid because one dll could have changed that.
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Cegcc-devel mailing list
> Cegcc-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/cegcc-devel
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Reply via email to