Urho 1.7 android build error

There’s an error which still persist on android build of IK.

[ 43%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/node.c.o
[ 44%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/ordered_vector.c.o
[ 44%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/quat.c.o
[ 44%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/solver.c.o
[ 44%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/solver_1bone.c.o
[ 44%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/solver_2bone.c.o
[ 44%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/solver_FABRIK.c.o
[ 44%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/solver_MSD.c.o
[ 44%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/util.c.o
[ 45%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/vec3.c.o
[ 45%] Building C object Source/ThirdParty/ik/CMakeFiles/ik.dir/src/platform/linux/backtrace_linux.c.o
/usr/local/Urho/Urho3D-1.7/Source/ThirdParty/ik/src/platform/linux/backtrace_linux.c:2:10: fatal error:
‘execinfo.h’ file not found
#include <execinfo.h>
1 error generated.
make[3]: *** [Source/ThirdParty/ik/CMakeFiles/ik.dir/src/platform/linux/backtrace_linux.c.o] Error 1
make[2]: *** [Source/ThirdParty/ik/CMakeFiles/ik.dir/all] Error 2
make[1]: *** [Source/Urho3D/CMakeFiles/Urho3D.dir/rule] Error 2
make: *** [Urho3D] Error 2
Done building Debug Library for android in /usr/local/Urho/Urho3D-1.7/build/android/Debug/armeabi-v7a

as already noted by @Pencheff here

I think it takes a guard there… gave me no error while building on Os X… maybe the system “incorrectly” mistake android for linux?

If you believe this is a bug then you should report it in the Urho Github issue tracker. Thanks.
Will have a look later regardless. :smile:

Please check out the latest commit in the master branch. It should fix the debug build configuration for Android platform.

Sometimes I think that you are more improtant for Urho than all other contributors taken together. BTW, is it hard to maintain build system?

1 Like

No, not at all. When I started to look at this, I was a CMake newbie as well. The only advantage I have is years of Unix experience for scripting.

Goddammit! It works!