Linker errors with compiled libraries on OS X

[birarda]

On OS X 10.9.3 I'm having issues linking the compiled rtmidi libraries, static or dynamic.

Both cause me to get a linker error no matter what API function I call from my application.

I've defined MACOSX_CORE.

Undefined symbols for architecture x86_64:
  "RtMidi::getCompiledApi(std::vector<RtMidi::Api, std::allocator<RtMidi::Api> >&)", referenced from:
      Application::Application(int&, char**, QElapsedTimer&) in Application.o

[garyscavone]

Hi Stephen,

Did you figure out your problem? It seems you are using Qt and from my experience, you can get linker errors because the SDK that Qt is pointing to is different from the one it was compiled with.

—gary

On Jun 30, 2014, at 5:40 PM, Stephen Birarda notifications@github.com wrote:

On OS X 10.9.3 I'm having issues linking the compiled rtmidi libraries, static or dynamic.

Both cause me to get a linker error no matter what API function I call from my application.

I've defined MACOSX_CORE.

Undefined symbols for architecture x86_64:
"RtMidi::getCompiledApi(std::vector<RtMidi::Api, std::allocatorRtMidi::Api >&)", referenced from:
Application::Application(int&, char**, QElapsedTimer&) in Application.o

—
Reply to this email directly or view it on GitHub.

[birarda]

Does RtMidi require Qt to build?

Edit: It does not, from what I can see. Maybe I'm confused about what you mean.

[garyscavone]

Not at all. I was just pointing out that if you try to use RtMidi together with Qt (which appeared to be the case), then linker errors can result because of the Qt settings.

—gary

On Jul 7, 2014, at 2:29 PM, Stephen Birarda notifications@github.com wrote:

Does RtMidi require Qt to build?

—
Reply to this email directly or view it on GitHub.

[birarda]

Ahh - are you talking about the OS X SDK?

[garyscavone]

OK, I was confused by the “Application” reference.

Anyway, is this still a problem?

—gary

On Jul 7, 2014, at 2:42 PM, Stephen Birarda notifications@github.com wrote:

Ahh - are you talking about the OS X SDK?

—
Reply to this email directly or view it on GitHub.

[birarda]

Yeah - if I compile RtMidi and then link to the static or dynamic libs I get this. No error if I just include the RtMidi header and cpp file in my project.

[drewish]

I ran into a similar sounding issue on another project. Worth making sure both are linking to the same stdlib.

[birarda]

Awesome @drewish I think you nailed it.

Clang defaults to compile RtMidi with libc++ and our project is libstdc++ causing linker errors with std::string. Now I just have to figure out why clang cannot find the OS X framework headers if I try to compile with libstdc++.

[drewish]

See if dberesford/exiv2node#26 has any clues.

[MartinDelille]

Can RtMidi be compiled with libstdc++ to avoid this problem?

[birarda]

To avoid having to fix this with other dependencies in the future anyways we're going to move our project over to libc++. Thanks for helping me figure this out!

[MartinDelille]

👍 For now it's working including the file directly in the project and defining MACOSX_CORE

[drewish]

@garyscavone I think this can be closed.