Forum Replies Created
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 packets
The 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.
The PATH bug has been fixed in VisualGDB 2.1. Please also use NDK r8 or newer.
We have fixed the bugs you mentioned in VisualGDB 2.1. If you encounter any further problems, feel free to post here.
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.
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.
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.
You need to install Visual Studio SDK
It is indeed LGPL. If you need a commercial license or a customized version, use the contact link on the website.
thanks. I’ll have a look.
That’s the default behavior in Windows Vista and Win7.
You can use VisualDDK to override it.April 3, 2012 at 09:02 in reply to: no menu visualddk after installing VisualGDB [Solved] #2037
Hi, please run the following commands:
devenv /resetaddin VisualGDB.AddIn
devenv /resetaddin DDKDebugConsole.Connect
devenv /resetaddin DDKDebugLauncher.Connect
devenv /resetaddin DDKProjectProperties.Connect
It will reset all addin settings.
If this does not help, please execute the Tools->Addins command in Visual Studio and ensure that all VisualDDK addins are enabled.
Note that if you import previously saved Visual Studio settings after installing VisualGDB/VisualDDK, the newly created menus will be reset. Running /resetaddin will always restore the add-in menus to their default state.
I will add the possibility to choose associated extensions to the next version.
However, has WinCDEmu never associated itself with RAR file. If you’re getting problems with them, they are probably caused by the Universal Extractor, not WinCDEmu.
Hi, Step 7 is very important. You need to replace the original version of VBoxDD.dll by the special version provided by VirtualKD. This will force VirtualBox to create a special virtual device that will allow the OS to communicate with VisualDDK.
Note that the original VBoxDD.dll should be renamed to VBoxDD0.dll, so that the modified version can actually find it.
getenv() is a function for normal applications, not drivers.
To get process environment from the driver you’ll probably need to parse the PEB structure.
Try googling or looking into ReactOS sources for more details.