Forum Replies Created
-
Posts
-
Hi,
Just adding the include directory is not enough to use the library, the shared library needs to be included in the app package and deployed together with it. Also, how to do this differs on Android from usual gcc projects.
We have a tutorial on making library-only projects with VisualGDB and adding those libraries to app projects:
http://visualgdb.com/tutorials/android/library/If in your case you just have the built library already without a project, then just the points 8 and 12 are important in your case. You should add a System.loadLibrary call as in step 8 and PREBUILT_SHARED_LIBRARY block (with your library paths) with LOCAL_SHARED_LIBRARIES specified as in step 12.
Please also note that the library you use must have been previously built targeting the Android OS.
Hi,
Based on the logs provided, the build is a debug build and the symbols for your app are loaded.
The message “No symbol “disassembly” in current context.” is a harmless warning to a gdb initialization command, it is not related to breakpoints not being set.
Please provide us with a full gdb log. For this, enable gdb logging on the GDB settings page in VisualGDB Project Properties. Then start debugging, replicate your scenario (make sure some breakpoints are set in the code before or during debugging), stop debugging and give us the log from your project directory.
Hi,
Please read our STM32F4 tutorial on the topic for hints:
http://visualgdb.com/tutorials/arm/stm32/fpu/Hi,
qmake generates the Makefile. When building, VisualGDB first calls qmake then make, hence the Makefile is always regenerated. The Makefile contents are based on the platform config file (probably /usr/share/qt5/mkspecs/arm-linux-gnueabihf subdirectory of the sysroot directory of the toolchain).
We will also be looking into reproducing the issue.Hi,
Passphrase support was added in one of the r releases of VisualGDB version 4.1, please try updating VisualGDB to the latest release at http://visualgdb.com/download/
Hi,
Currently no, the local IntelliSense directories are added as absolute paths only. There is no clear directory they should be relative to.
What is your use case here?Hi,
This is strange, it looks almost looks like the same command gets a different reply. Hence a few troubleshooting questions below that can help clarify the issue.
1. When you run the command manually, are you running the exact same command “D:Androidsdkplatform-toolsadb.exe devices” i.e. definitely calling the same adb.exe?
2. Are you running Visual Studio and cmd.exe with different user rights i.e. one in admin mode the other not?
3. Is the complete adb log the following i.e. no “List of devices attached” line anywhere: ?D:Androidsdkplatform-toolsadb.exe devices Command exited with code 04. Are the connected devices sleeping (i.e. screen locked) when trying to debug with VisualGDB?
5. Which exact versions of Android SDK Tools, Android SDK Platform-tools, Android SDK Build-tools are you using? You can get the version numbers from the Android SDK Manager.
6. Which version of VisualGDB are you using?Hi,
Based on this log and the line “warning : unknown QT: multimediawidgets”, you need a space in between i.e. “multimedia widgets”.
Based on “/usr/bin/ld: cannot find -lQtMultimedia”, libQtMultimedia cannot be found by the linker. Please verify that libQtMultimedia is installed on your Raspberry Pi (should be somewhere in /usr/lib where the other Qt libraries are).
As other Qt libraries are found, the standard Qt package for Raspberry Pi may not include it and you should install it separately. You may also need to build the library yourself if it is not available anywhere.Hi,
VisualGDB uses the exact same “adb devices” command to locate devices. What is the exact error you are getting while debugging? Please try reconnecting the device.
Hi,
The .pro file with your project name contains the QT statement you should add “multimedia” to. qmake is always run automatically by VisualGDB when building.
Hi,
Please try the newly released VisualGDB version 4.1r10 (http://visualgdb.com/download/).
It includes extended GUI support for the Hardware Registers window, all three levels are now shown, the subregister values can be viewed and edited.
Hi,
Please try the newly released VisualGDB version 4.1r10 (http://visualgdb.com/download/).
It includes a fix to third-party toolchain importing. We also added a possibility to edit local folders instead of using the usual Windows folder browser.
Hi,
Glad to hear that things are working now. Installing VS in a non-default path should not be related, as VisualGDB uses the VS path from the registry.
Hi,
It could be a broken Visual Studio installation issue. Did you install Visual Studio for c/c++ ? Generic settings should have this included, if you chose VB.NET only then c/c++ will not be included.
Which type of VisualGDB project are you trying to make?Hi,
VisualGDB does support building the apps and debugging the c/c++ code of both Qt4 and Qt5 on Raspberry Pi and Beaglebone.
However, before you make the Qt5 project with VisualGDB you should setup Qt5 manually on the platform, that may mean building it from sources. Installing Qt5 from a package is not yet available for Raspberry Pi or Beaglebone, only for generic x86 Linux platforms. Hence the VisualGDB project wizard cannot install Qt5 for you.
