Forum Replies Created
-
Posts
-
Hi,
Since VisualGDB 2.4 the external tar.exe is no longer required. Please update your VisualGDB installation.Please use the shell function provided by GNU Make. E.g.:
LIBRARY_NAMES :=pthread $(shell pkg-config --libs uuid) $(shell mysql_config --libs)Hi. Did you install VisualGDB from the same user account you are using now?
Normally, the installer creates VisualGDB.AddIn file and puts it to C:UsersDocumentsVisual Studio 2008Addins. If it fails, VisualGDB Wizard shows you a diagnostic window allowing to re-install the file:
It’s described in more details here: http://visualgdb.com/KB/?ProblemID=noaddinDo you get the diagnostic window? What happens when you press “Rebuild Add-In file”? Do you have the DocumentsVisual Studio 2008Addins folder and is it writable for your current user account?
We have tested it with VMWare and did not encounter any problems.
There can be several reasons why the auto-detect is not working:
1. Windows firewall might block it
2. Linux firewall might block it
3. Some antivirus software might block broadcast packetsThe easiest way to fix it is to add another host-only network card to VMWare. Ensure that it gets a valid IP address by running sudo ifconfig. If not, run sudo dhclient to re-acquire a dynamic address.
Note that if the build server is not printing “discovery request from …” messages, the packets don’t reach the VM, and if it is printing this but nothing is detected, the problem is on the way back.
We have fixed the bugs you mentioned in VisualGDB 2.1. If you encounter any further problems, feel free to post here.
Hi,
Thanks for reporting the bug. We’ll add support for the trailing ” in the next version. As a workaround, you can modify the LOCAL_SRC_FILES statement to fit all source files on 1 line (without the ” character anywhere). Then VisualGDB will parse and update it correctly.
Note that the MK file is updated each time you build the project from Visual Studio and not when you actually delete or add the files.
We will also add the explicit platform specification to ndk-build in the next version. As a workaround, you can build the project using ndk-build until we release the new version. The deployment and debugging will still work as expected.
Hi,
This happens due to a PATH conflict with another GNU-based toolchain on your computer (such as WinAVR).When Android tools are invoked, a wrong version of sh.exe gets executed and it breaks down the compilation.
Please remove all directories that can contain sh.exe and similar tools from the PATH variable before starting Visual Studio. Note that you might need to restart your computer after modfying the PATH variable in system settings.Hi. Depends on whether you want to build Windows or Linux apps.
The easiest way would be to setup the command-line build using QT tools and then create a “wrapper project” with VisualGDB.
This is a one-time “time investment”. Once the wrapper project is created, building and debugging it would be a matter of executing one command.If you want to build remote Linux apps, check out this tutorial.
A tutorial about wrapping existing projects is here: http://visualgdb.com/tutorials/gnudebugHi,
Just leave the default settings and press OK.
You can also set the “Manage drive letters automatically” checkbox. Then the dialog won’t appear again.It is indeed LGPL. If you need a commercial license or a customized version, use the contact link on the website.
