Different behavior of Clang vs. gcc in OS-X
-
Hi together!
Actually im trying to get my project working in OS-X again. The project is completely plugin-based. There is a big project tree with a lot of sub-projects compiled as binary plugins.
If I compile it with clang, the plugins doesn't get loaded. It seems that clang ignores the include locations - given in *.pro file - of external librarys. With gcc all works fine - except the plugins which are using C++11.But on the other hand, I need C++11 support. The pre-installed gcc can't compile C++11. So what do you recommend?
Every hint is welcome...Thanks in advance!
Frime -
Hi,
Did you add
CONFIG += c++11to your pro file(s) ? -
Thanks for your response!
Clang compiles it without any errors, but gcc doesn't ...
The problems building my project with clang are really weird. There appear really strange runtime errors, which doesn't make any sense. My plugins can't be upcasted anymore (via qobject_cast), some singleton implementations return 0 pointers via instance() (after they have been already initialized).The same code works without any problems on windows and linux...
Can some different compilers really influence the runtime-behavior so hard?Thanks in advance,
frime -
What errors are you getting ?
