Shared Library in Release, build stall on the 2nd source file

Shared Library in Release, build stall on the 2nd source file

BY 26 Jun 2013 Native Application Development

Hi,

I have succeeded to build my c++ native priojects in ‘x86’ architecture, static lib (.a) + shared lib (.so) + executable, runtime works fine on the emulator,

but when I build for ‘ARMv7-a’ architecture to test on a device, my shared lib build stalls everytime on the 2nd source file, only the first cpp file is builded, so no .so library are created, and no errors displayed on log or console… (however the static library builds fine in this architecture)
I tried to invert or delete some files, and still only the first alphabetic file is builded :/
I tried to create a new project with only 2 .cpp files, and have the same problem.

does anyone have encountered this problem ???

Tizen SDK 2.1 under windows

thx,
nico

ps: it works with “GCC-4.5” instead of “LLVM-3.1”

Written by