On Jun 7, 2017 3:19 PM, "Brad Garton" <gar...@columbia.edu> wrote:
I wish I could (go the total mingw-w64 route). The libs I'm building are for use in OpenFrameworks and Unity, and I don't think mingw-w64 projects exist for them. OpenFrameworks had good support for mingw-w64 via msys2 stuff last time I checked. Unity is another question but it's likely possible to make mingw-w64 import libraries for their DLLs. brad On Wed, Jun 7, 2017 at 10:08 AM, David Grayson <davidegray...@gmail.com> wrote: > I'd encourage you to try the mingw-w64 route. If you use mingw-w64 > and GCC, you won't have to worry about the licensing restrictions > Microsoft puts on Visual Studio, which have changed over the years. > The mingw-w64 project provides a lot of the headers and functions that > Visual Studio has, and they always accept patches to add missing > headers or functions on this mailing list. In fact, I've been able to > compile two different pieces of pretty involved Microsoft sample code > using mingw-w64 (usbview and devcon). > > --David > > On Wed, Jun 7, 2017 at 6:35 AM, Brad Garton <gar...@columbia.edu> wrote: > > Aha -- this was what I feared would be the case. I'll start porting all > > the code into VS and tracking down all the missing headers and functions, > > oh joy. > > > > Thanks for the help, everyone! > > > > brad > > > > > > On Wed, Jun 7, 2017 at 6:50 AM, Mateusz Mikuła <mati...@gmail.com> > wrote: > > > >> > However, once I try to use some more c++ features, I get the > >> > following > >> > error, and it seems to be associated with the compiled object files > >> > themselves: > >> > > >> > "invalid or corrupt file: no symbol for COMDAT section ..." (and a > >> > hex > >> > address). > >> > >> It's not possible to mix static libstdc++ with Microsoft C++ runtime. > >> In fact even mingw-w64 based Clang doesn't play nicely with static > >> libstdc++ http://lists.llvm.org/pipermail/cfe-dev/2017-April/053530.htm > >> l > >> ------------------------------------------------------------ > >> ------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> _______________________________________________ > >> Mingw-w64-public mailing list > >> Mingw-w64-public@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > >> > >> > > ------------------------------------------------------------ > ------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Mingw-w64-public mailing list > > Mingw-w64-public@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Mingw-w64-public mailing list > Mingw-w64-public@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
