[Emre]

Hey, I’d really like to use your platform but here’s the error code we receive right out of the gate:

It is weird because it seems that it is related to libstdc++

 

Undefined symbols for architecture x86_64:

“std::string::_Rep::_M_destroy(std::allocator<char> const&)”, referenced from:

ParticleItem::createParticlesFromFile() in libVPlay.a(particleitem.o)

“std::string::_Rep::_S_empty_rep_storage”, referenced from:

ParticleItem::createParticlesFromFile() in libVPlay.a(particleitem.o)

“std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(char const*, unsigned long, std::allocator<char> const&)”, referenced from:

ParticleItem::createParticlesFromFile() in libVPlay.a(particleitem.o)

“std::ios_base::Init::Init()”, referenced from:

__GLOBAL__sub_I_json.cpp in libVPlay.a(json.o)

“std::ios_base::Init::~Init()”, referenced from:

__GLOBAL__sub_I_json.cpp in libVPlay.a(json.o)

ld: symbol(s) not found for architecture x86_64

clang: error: linker command failed with exit code 1 (use -v to see invocation)

make: *** [GymGame.app/Contents/MacOS/GymGame] Error 1

01:47:53: The process “/usr/bin/make” exited with code 2.

Error while building/deploying project GymGame (kit: Desktop Qt 5.5.1 clang 64bit)

When executing step “Make”

[GüntherFelgo Team]

Hi Emre!
First of all, Merry Christmas! 😉 … and sorry that you had to start this special day with build problems!

Let’s see if I can help you:
Which project did you try to build – does this error also happen with a New Empty Felgo 2 project (created with the “New Project” wizard in Qt Creator)?
Are you using the latest OSX and Felgo version or maybe an older one? (I currently use Felgo 2.6.2 on Yosemite and El Capitan – never had that error)
Best,
Günther

• This reply was modified 8 years, 3 months ago by  GT.

[Emre]

Hi Gunther,

 

It is the latest vplay, 2.6.2 and OS X Yosemite 10.10.5

 

It is a build error, cmake/make related something.

[Emre]

Hey, I think I know what the problem is; it’s the following directive in my .pro file:

CONFIG += c++11

The problem is I really need this for the rest of the app to work. Any suggestions?

 

Thanks,

[AlexFelgo Team]

Hi Emre,

The issue indeed comes from a different libstdc library being linked when using C++11. Could you please have a look at the linker output and check which standard library is getting linked? Probably adding

LIBS += -lc++

does solve that issue?

Thanks,

Alex