[megaderek]

Just an update I see that the same thing occurs in Android Studio so its probably not the fault of VisualGDB.

[megaderek]

Here is a screenshot.

Attachments:

You must be logged in to view attached files.

[megaderek]

I would definitely like to try it out. I have a couple of large projects that were built using VisualGDB 4 and some new ones planned.

[megaderek]

I tried rolling back the SDK version but I think CMake is permanent in Android Studio 3, new projects with C++ are automatically configured to use CMake. So I uninstalled and tried the last version of Android Studio 2.x prior to them introducing CMake. I managed to import the native-activity from the ndk-build branch of the NDK Samples into Android Studio, build and run. I then imported it into VisualGDB, although I was still required to resolve some issues with the native build side of things. It runs now but can’t be debugged (debuggable is true) VisualGDB pops up a warning saying “trying to debug an older version of the app, Please reinstall the app on the device” I guess there is something broken about it that I don’t understand.

I’ve also tried importing the plain VisualGDB Android Project Wizard into Android Studio in the hope that it will convert it to the gradle system which can then be re-imported into VisualGDB. Usually there is something that will break along the way. Unfortunately a lot of this requires intimate knowledge of the how the Android build system works.

It would be good to have the possibility to create a new Android project with the VisualGDB Wizard that allows you to choose Gradle support. Either that or CMake support would probably solve my issues.

Is there an ETA on CMake support for Android?

 

[megaderek]

Hi thanks I tried signing the debug version but jarsigner refused saying there was an incorrect size of something in the APK.

I just did a test and it looks like I can run the debug build from the debugger and my Google IAB code can query product details successfully. (Not sure if purchases will work with an unsigned debug build) however I ended up making a console window in my app so I can see debug trace statements without the debugger if needed.

[Author]

Posts