On Wed, 2009-11-18 at 14:18 +0100, Vincent R. wrote:
> On Wed, 18 Nov 2009 14:14:42 +0100, Pierre Ynard <[email protected]>
> wrote:
> > I just got replied this:
> >
> > http://lists.gnu.org/archive/html/bug-gnu-libiconv/2009-11/msg00006.html
> >
> > What should I tell him? More generally, is there any MSDN resource
> > documenting what features are available or not on WinCE? How do you guys
> > know when to #ifndef a function declaration or not?
>
> You could for instance send the coredll.def file since it lists all PUBLIC
> available functions.
And obviously all of MSDN documents which version of the operating
system supports which API. You can use that for the #ifdefs.
Bruno Haible wrote :
> The documentation of the Windows runtime libraries, especially of errno [1]
> and setlocale [2], gives no indication that these parts of the runtime
> library would be missing on Windows CE. Therefore I would assume that the
> lack of these facilities is an omission in CeGCC.
I can think of two answers to this.
1. Bruno is confusing the capabilities of CE with the APIs supported by
cegcc : it can be debated whether a compiler needs to support a
feature not supported by the target operating system.
2. Bruno doesn't know about arm-mingw32ce vs arm-cegcc. The latter is
designed to support exactly this kind of stuff. arm-mingw32ce is
designed to support just the CE API.
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Cegcc-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cegcc-devel
