I'll need a bit of help to figure out what's wrong.
I've just done a complete rebuild of both arm-mingw32ce and
i386-mingw32ce, both on Linux. I am referring to the gcc-4.4.0 build. I
assume that you do so too, otherwise we wouldn't be talking about gcc_s,
right ?
If *that* is the issue, then the
Hi,
>> I'm trying to create a C++ DLL with the mingw32ce toolchain (v0.55 from
>> SF). But the DLL depends on libstdc++-6.DLL instead of statically
>> linking in the necessary stuff. Is that intended?
>>
>
> If you don't want to link with a DLL, specify -static . Or don't install
> the DLL
On Wed, 2009-06-03 at 17:32 +0200, Klaus Rechert wrote:
> I'm trying to create a C++ DLL with the mingw32ce toolchain (v0.55 from
> SF). But the DLL depends on libstdc++-6.DLL instead of statically
> linking in the necessary stuff. Is that intended?
If you don't want to link with a DLL, specify
Hey,
I have compiled with mingw32ce the version of iconv that can be found
here:
http://yukihiro.nakadaira.googlepages.com/
(version which is used by glib, btw). It has a smaller footprint than GNU
libiconv, so it should be perfect for embedded devices.
You can find the packages here:
http:
Hi all,
I'm trying to create a C++ DLL with the mingw32ce toolchain (v0.55 from
SF). But the DLL depends on libstdc++-6.DLL instead of statically
linking in the necessary stuff. Is that intended?
Second: copying libstd++-6.dll to the device and starting a program
results in a "not enough memor
On Wed, 3 Jun 2009 07:44:35 +0200, Danny Backx
wrote:
> It looks related
>
> Danny Backx - danny.backx - at scarlet.be ; http://danny.backx.info
>
> -Original Message-
>
> Don't know yet if it has something to do with latest modification on
trunk
> or if it's platform specific.
I can
