The details of C++ ABI on Windows are not standardized at all, unlike the different C calling conventions (stdcall, PASCAL etc.). GCC and MSVC have completely different implementations and the resultling binaries will be in no way compatible.
I also wonder how all these package managers deal with the fact that it is possible with MSVC to pick compiler and linker settings that result in mutually incompatible libraries. Do they impose restrictions on the compiler flags that can be used in the scripts? ________________________________ From: Oiio-dev <[email protected]> on behalf of Will Rosecrans <[email protected]> Sent: 03 January 2017 19:05 To: OpenImageIO developers Subject: Re: [Oiio-dev] Easier Windows builds What are the implications of trying to link a gcc-cross compiled OIIO built on Linux with a MSVC built application built on Windows? Won't the ABI be different between the build environments since OIIO exports a C++ API rather than just using C++ internally and exporting a C API for users of the library? On Tue, Jan 3, 2017 at 5:45 AM, Richard Shaw <[email protected]<mailto:[email protected]>> wrote: Probably not terribly helpful but in my experience it's much easier to cross-compile from linux than to build on windows natively... If I have time I may give it a whirl, Fedora has one of the best mingw development environments I've seen. Thanks, Richard _______________________________________________ Oiio-dev mailing list [email protected]<mailto:[email protected]> http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
