[ket]

Hi,

We do not have a specific tutorial on that, but the setup should not differ much from usual VisualGDB Linux projects. Hence please look at the Linux tutorials (e.g. http://visualgdb.com/tutorials/linux/) for help.

[ket]

Hi,

In Visual Studio please find the Output window. If it is not shown, then you can make it shown from the View menu. The full log of the build is in shown in the Output window. The error list is only meant for errors that relate to source code lines e.g. syntax errors. Other types of errors can happen during a build e.g. library linking problems or problems with Android tool setups. The error you listed means that the build failed, but the error could not be mapped to source code. Hence you should read the full build log from the Output window to understand the cause and fix it.

[ket]

Hi,

Our knowledge base article at http://visualgdb.com/KB/?ProblemID=nopkg contains the description of two problems about Android device images. Have you checked for the second problem?
As the device you are using is a Galaxy device it likely has the problem with its device image. In that case please try updating your Android device, try the fixes suggested in the official Google bug thread or use another Android device for debugging.

[ket]

Hi,

Getting the linking syntax correct in Android makefiles can be tricky as different path syntax is expected for different variables. Some variable values only work with relative paths or paths relative to LOCAL_PATH. VisualGDB only passes the makefiles along to make, so the problem must lie within the makefiles.
VisualGDB handles the library dependencies of projects inside the same solution automatically if you set project dependencies. With the logic VisualGDB uses for its library dependencies each library project is built separately when VS builds them, the projects dependent on other library projects do not rebuild them.
Have you tried looking at our Android library tutorial for help?

[ket]

Hi,

For which target are you searching a toolchain for? There are a variety of different toolchains available on our site at http://gnutoolchains.com/ .

[ket]

Hi,

Which platforms do you have installed?

Please note that 4.4W and L platforms do not yet show up in the VisualGDB installed platforms list. This will be added in the next r release of VisualGDB.

[ket]

Hi,

Please refer to the wiringPi tutorial for an example on how to use libraries with cross-toolchains:
http://visualgdb.com/tutorials/raspberry/wiringPi/

In short you need to resynchronize the sysroot of the toolchain and add the library name to the list of libraries in the makefile.

[ket]

Hi,

VisualGDB projects do not use settings specified in Properties, VisualGDB Project Properties should be used instead.

The include directory should be specified in the Android.mk file, accessible also through VisualGDB Project Properties->Makefile settings.

[ket]

Hi,

Debugging of release builds is normally not possible, the Android OS checks the flags as well and the debugging symbols are stripped from release builds anyway.
Do you only need to use your key to sign the debug build instead of the automatically generated debug key?
If that is the case then you could try signing the unaligned debug build (retained in bin) manually with your key and using that apk for debugging.

[ket]

Hi,

The trial version is fully featured, so that is not the problem.

The “synchronize sysroot” button is usually disabled if you are not using a cross-toolchain but instead building on the Raspberry Pi itself. On the Project settings page in VisualGDB Project Properties what is the “remote computer used for building and debugging”? Also what is the toolchain name next to the “synchronize sysroot” button?

[ket]

Hi,

Could you please give more details on the issue? Are you using a virtual Android device? Is VisualGDB being run from a VM? What exactly do you mean by finishing initializing? Can you give some examples of the commands that time out?

Also, what issues do you get building the imported project in Visual Studio? The project imported as in our co-debugging tutorial should be compilable in VS whether the sources are added to the Solution Explorer or not.

[ket]

Hi,

The Hardware Registers window opens automatically during debugging when supported by the board support package. Currently MSP430 and STM32 devices have support for the Hardware Registers window. If you are debugging a supported device but cannot see the window, then you can show it manually at Debug->Windows->Hardware Registers.

[ket]

Hi,

VisualGDB handles the c/c++ parts of Android development. We do recommend using a Java IDE in parallel e.g. for co-debugging. You could try using Android Studio, but it uses a different project format. If you import the project to it with choosing to maintain a link to the eclipse project format, then it could work. The other option is to edit the project files yourself, but that is not very well documented (e.g. http://developer.android.com/tools/projects/projects-cmdline.html). Importing the project to eclipse is quite a lightweight solution and will not add many additional files.

[ket]

Hi,

VisualGDB uses grouping flags for libraries in its generated makefiles to avoid any dependency order issues. In your .mak files do you have the following specified?

START_GROUP := -Wl,--start-group
END_GROUP := -Wl,--end-group

[ket]

Hi,

The Raspberry Pi toolchain creates executable files in the elf format.

[Author]

Posts