externalNativeBuild, range = [0xcb41e82c-0xcb41e970), name='Clory::Engine::instance(Clory::RuntimeConfiguration const&, Clory::Engine::Purpose)', mangled='_ZN4Clory2Engine8instanceERKNS_20RuntimeConfigurationENS0_7PurposeE'įirst of all, there was no CompileUnit section in the result of the command image lookup -vrn Clory::Engine::instance. The adle file specifies the CMakeLists.txt file which configures the C++ layer. The debugger works, I can step inside the Java_clory_engine_sdk_CloryNative_nativeInit function, but I would also like to further debug the library corresponding to the Clory::Engine class which, as I mentioned, is an internal library we have source code access to.įor example, Clory::Engine::instance is part of the library and I would like to specify to Android Studio the location of the CloryEngine.cpp file so I can step inside Clory::Engine::instance with the debugger, thus debugging this static member function. Having access to the library source code, is it possible to specify to Android Studio the path to the source code so I can step inside the library using the debugger? The C++ library is a company internal library and we have access to its source code, but in the Android project it is only dynamically linked, so it is used only in the form of headers (.

I'm working on an Android project which uses a Java class that is a wrapper on a C++ library.

Android studio c#