Re: [Mingw-w64-public] Compiler toolchain for embedded windows platform

[JonY <jo...@us...>]

On 5/26/2012 00:32, Alberto Luaces wrote:
> Hello,
> 
> I'm trying to deploy a DLL to be run in a windows-based, embedded
> device.  In order to compile it, I have used mingw w64.  The DLL works
> fine on windows in a regular PC.  However, it fails to load when the
> used from the device.  The reason is that the device has a MSVCRT.DLL
> library that lacks some functions that seem that are expected in
> programs compiled with mingw w64.  So far, __setusermatherr is not
> defined there, and some more symbols might not be found in advance.
> 
> I thought of building a mingw w64 toolchain not relying on MSVCRT.DLL,
> by using newlib instead, but I'm having trouble doing that: latest
> newlib expects libppl=0.10 and the latter doesn't compile on my system
> (but libppl 0.12 does)...  so I guess maybe it is better to seek for
> advice on this list about having a mingw w64 toolchain whose produced
> binaries don't rely on MSVCRT.DLL.  Specifically I would be interested
> on seeing how other people build their own cross-compilers for embedded
> systems, dealing with the libc issue.

Well, you're the first to try mingw-w64 for an embedded Windows, so I
wouldn't expect it to go smoothly. It'll take some modifications to
continue.

The best way to find out is generate the def files for the embedded
gdi32, comdlg32, user32, kernel32, advapi32, shell32 and msvcrt DLLs.
You can look for the gendef tool to help you out.