Forum Replies Created
Could you please post your AndroidManifest.xml file here?
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
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 endif
No 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 RELEASE
If 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.
Fixed. Please download VirtualKD 2.8 and replace the files in VisualDDK folder.
OK, if you encounter the problem again, feel free to submit details so that we can fix it.
The problem with vs-android is that Google may change some NDK internals one day making the hardcoded settings in vs-android unusable (or even worse, producing some hidden hard-to-pinpoint bugs). If you’re interested, I can instruct you how to configure VisualGDB to debug your vs-android projects.
Which exact Linux version and GDB version are you using?
Please try disabling the firewall on both Windows and Linux.
If this does not help, please add a separate network card to your VM configured in the Host-only mode.
Thanks for your appreciation!
Updating is even easier, you don’t need to uninstall the previous version. Just run the new installer and it will update your files.
Project folder support will be enabled automatically for all projects, both old and new.
If you are using BazisLib, please use the npagednew() function. Otherwise, use the ExAllocatePool() API provided by Windows Kernel.July 8, 2012 at 12:29 in reply to: No debugging logs from win32 applications in vista or seven #2214
That’s the default behavior in Windows Vista and later. Please have a look here: http://www.osronline.com/article.cfm?article=295July 8, 2012 at 12:27 in reply to: VisualDDK crashes when attaching to VMWare Windows 7 64bit g #2158
Hi. Please try the new VisualDDK 1.5.7.