On 3/26/2013 19:47, Etienne Sandré-Chardonnal wrote: > Dear all, > > However, I got two new issues: > - zlib installed its headers in /mingw/include, this means in the > main mingw include folder. However, this one is not in mingw header > search path, which is in i686-w64-mingw32/include along with all the > stdlib headers. This means I have to move manually the zlib installed > files.
Likely because it is a cross compiler. You did have to use --host. > - The configure and make steps of openEXR stopped because they were > missing "libgcc_s_sjlj-1.dll" to lauch some executables. So I copied > them into the main bin folder along with the host-prefixed > executables. > Ditto, target binaries do not mix with host executables. Just because Windows runs both executable and DLL does not mean it is the same triplet. What you want is a native compiler where build==host==target. You can do this yourself, or ask someone on this list to do it. Doing it yourself isn't hard, gets you out of the dependence mindset, just go ahead and ask if you are not sure what to do. > So to conclude : what is the proper way? Which environments, mounts, > autoconf options etc... should I use to have everything working with > the mingw out of the box file structure? From your message, looks like you got things to work.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
