09 PM, Ray Donnelly
wrote:
> 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.
>
>
>
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 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 wrote:
> > However, once I try to use some more c++ fea
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
and MSVC. I wish there were an
option for "nm" or a libtool that would help me fix this.
Any ideas?
thanks --
Brad Garton
Columbia University Computer Music Center
--
Check out the vibrant tech community on one
