aha! I didn't realize qtcreator was an msys2 project for OpenFrameworks!
Thanks!
Unity is another story. Their basic scripting language is c# (yikes) so
not sure if it will work or not. It took a bit of wrangling to get the lib
working with Unity on OSX.
brad
On Wed, Jun 7, 2017 at 12:09 PM,
On Jun 7, 2017 3:19 PM, "Brad Garton" 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. Uni
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.
brad
On Wed, Jun 7, 2017 at 10:08 AM, David Grayson
wrote:
> I'd encourage you to try the mingw-w64 route. If you use mingw-w64
>
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 the
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 wrote:
> > However, once I try to use some more c++ fea
> 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 Mi
Mixing C++ from different compilers is one of the ultimate adventurous
roads to go. Nevertheless you can still share C API instead.
Anyway, if you want to use mingw-w64 together with VS, I would
recomment to switch to Clang for mingw-w64 (llvm). It is capable to
produce mostly compatible C++ code
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
10 matches
Mail list logo
