Forum Replies Created
-
Posts
-
Hi,
You can fix this by adding the following line to Android.mk just before the “include $(BUILD_SHARED_LIBRARY)” line:
LOCAL_SHORT_COMMANDS := trueHi,
Sorry for the late reply.
VisualGDB cannot start debugging because the NDK build system fails to include gdbserver[/b[ into the application package. It might be related to your build problem.
Does the “*** target pattern contains no `%’.” message always appear? Does reinstalling NDK help?Looks like some old version of make.exe gets invoked. Could you please paste the entire build log here?
We are currently working on resolving VS2012 compatibility issues. Does the debugging work with VS2010?
Hi,
It’s a bug of the Android run-as tool. See this page for possible workarounds.Hi,
Which version of NDK and SDK are you using?
Are you using a custom Android.mk file? Could you please post it here or send to the support email?Which version of Android are you using and what exact device? It looks like the output of the ps command looks differently from the usual one.
When you are generating Android projects, the underlying makefile structure is 100% compatible with the classical NDK makefiles and thus adding new preprocessor definitions is done exactly like for the normal NDK projects (see
docsandroid-mk.html). In your case please add the following text to Android.mk (before the include $(BUILD_SHARED_LIBRARY) line):
ifeq ($(NDK_DEBUG),1) LOCAL_CFLAGS += -DDEBUG else LOCAL_CFLAGS += -DNDEBUG -DRELEASE endifNo problem. The definitions in the Project Settings indeed apply to IntelliSense only. To change the actual definitions, please edit the flags.mak file in the project directory. The default flags.mak file contains the following definitions:
COMMON_MACROS := DEBUG_MACROS := DEBUG RELEASE_MACROS := NDEBUG RELEASEIf it does not help, please rebuild the project and post the entire build log here. It will help understanding why the definitions were not applied.
