Hi Ronan,Hello,
For your information, I have investigated the possibility of using mxe for building our software relying on shared libgcc.
I have forked mxe in order to apply very few changes : git://github.com/rtrepos/mxe.git
It worked, not completely yet and only for our software, but exceptions sent by plugins are now caught by the main application.
I don't know much about shared libgcc, but the docs [1] indicate that it should be safe to enable in the gcc build since all the other package builds will use the static version when directed. It's also curious that libstdc++ is shared by default, but can be partially linked statically to freeze the version of libstdc++.
Nevertheless I had to use the latest repositories of mingw during Mingw installation on windows.
The version of gcc (4.6) provided by the default installation is not compatible with the one used by mxe on ubuntu 12.10 (4.7.0) (?)
Again, I've never tried it, but wouldn't you be able to use the library created by mxe and ship it with your application? It's probably somewhere under $(PREFIX)/lib/gcc instead of the usual $(PREFIX)/$(TARGET)/lib. If you have any comments on this (e.g. is it a bad idea to use mxe for this purpose) don't hesitate.
It seems that MXE provides exactly what we need, and even much more, so thank you for that.
There are plans to support dynamic builds in the future, but it's still a way off - any feedback in this direction is helpful so please let us know any hints you find (e.g. would setting --enable-shared in gmp.mk cause the correct LDFLAGS to be set?)
Thanks,
Tony
|