I’m trying to convert an eclipse project over to the nsight tegra edition for VS. Problem I’m getting is that it build the CPP fine (I had to hack it pretty heavily to work with android-ndk-r8d and give me full C++11 support mind!). Immediately after building the C++ it then just simply says “failed”.
Thanks for that. When is this next build going to be released?
I’m currently having all sorts of problems with neon code. I can’t get ARM_NEON to be defined. Manually defining it causes the arm_neon.h to throw loads of errors on the builtins.
Furthermore I can’t seem to find cpu-features.h …
Not to mention I can’t actually debug anything anyway as it complains about the gdbserver not being present … It does at least upload the code to the device.
I’d rather hoped that this would be LESS problematic than “standard” android development but as it is I’m currently finding it less usable with my Nexus 7 than I found eclipse and thats quite an achievement :(
Which is a real shame because I would love to do all my development with developer studio in some usable form.
NOTE: I use | throughout this post as a backslash replacement because forum engine keeps removing any backslashes I input.
If you have created the project with Nsight Tegra and Configuration Type is “Application (.so → .apk)”, then you could try to include cpu-features.h like this:
#include <machine|cpu-features.h>
This should work because ndk-root|platforms|android-14|arch-arm|usr|include is used for headers search by default.
It’s strange that you got messages about the missing gdbserver and even stranger that copying it to the output directory helped to fix the issue. Usually Nsight Tegra copies it from the installed NDK to libs|architecture-name folder in your project and binaries from that location are automatically packed into .apk. Could you by any chance provide us a sample project that fails to build or debug without copying the gdbserver to the output? That would greatly help to localize and fix the issue in our code.
If you look at machine|cpu-features.h you’ll see its not actually the file I’m after.
As for the gdbserver problem. Its quite possible that my hacking to make it work with android-ndk-r8d, x86 and mips has caused the issue so I’m not so worried. (This tool would be amazing if x86 and mips was supported as it would negate any reason to use eclipse. I know they’re not your supported platforms but it does leave me disinclined to use whats turning out to be an, otherwise, excellent tool)
I’d love to know how I can get support for the android.support.v4 library too.
Sorry for the wrong assumption about the cpu-features. Including android.support.v4 is not currently supported in Nsight Tegra. We are aware of this bug and will have it fixed.