On Tue, Jun 6, 2017 at 8:30 PM, David Grayson
wrote:
>
> Why do you want to build your application using both Visual Studio and
> MinGW? Why not pick one and stick with it?
It's the unix heritage. It's much easier to get it to compile with mingw,
but it looks like I'll have to go with buildin
C++ has no standard ABI, so it is unlikely that you will be able to
mix C++ binaries that come from different compilers like that. I'm
not sure what the COMDAT error means, though.
Why do you want to build your application using both Visual Studio and
MinGW? Why not pick one and stick with it?
Hello mingw list --
I'm a total newbie to this list, and I'm not even sure it's active, but
I've googled a lot and can't find much information so I thought I'd try a
post here.
I'm porting a large, unix-ey c/c++ package to Windows and I'm attempting to
compile a static lib that I can access in Vi
