Forum Replies Created
-
Posts
-
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.
Hi, please run the following commands:
devenv /resetaddin VisualGDB.AddIn
devenv /resetaddin DDKDebugConsole.Connect
devenv /resetaddin DDKDebugLauncher.Connect
devenv /resetaddin DDKProjectProperties.ConnectIt 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.
Hi,
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.Hi,
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.Hi.
I’m currently under very heavy load releasing BazisLib 3.0, several commercial projects that depend on it and making the new website.
I also have a list of features to add to WinCDEmu and I will hopefully find time around summer to do that.
As for the forum spam, I’m testing a semi-automated tool for cleaning it up, but again, I cannot promise to find time before summer to look more into it.
