Danny Backx wrote:

> MSDN says they exist in WinCE 4.0 and higher. So this raises the
> question again which version of CE we support. If I create a
> distribution that has support for these functions, then it won't work
> with CE 3.x devices.
> 

> A workaround for that might be to include the right tools for creating
> your own library files even in our binary distributions. Pedro, your
> opinion ?
> 

I'd like to avoid the complication that brings, until that is
really needed.  I don't see the need for it yet.  Always add the
functions to the import libs, and wrap the declarations in
_WIN32_WCE > XXX, XXX being the CE version they started being
defined at.  The stubs in the import libs are only sucked
into the images if they are called.  The only way for them to
be called will be:

- Wrong _WIN32_WCE defined by the user.  He gets what he asked for.
- The user declares the function himself, and the linker will not
   complain.  The loader will barf on the missing export from the
   corresponding dll.  The user got what he asked for - he should have
   realised which version of CE he was compiling to.

>> Finally, there seems to be a problem with the "PathCombine"
>> function (declared in "shlwapi.h"). I believe this is the
> 
> Is this the right patch ?
> 

Looks fine.

> +#ifndef        _WIN32_WCE

Please make that a simple space.

Cheers,
Pedro Alves



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Reply via email to