| Version 2 (modified by sagitario, 14 years ago) |
|---|
Known Issues
Please consult the ticket view for issues within Visual D. Some irritating behaveour is not caused by Visual D - these are listed here:
Visual Studio Express
Visual D does not work with any of the Express version of Visual Studio. These editions do not support loading third party extensions and add-ins.
A free alternative are the integrated Visual Studio Shell distributions, that can be downloaded here: (VS Shell 2008 and VS Shell 2010). The shells are identical with the Visual Studio IDE, but stripped of any language support. It still contains the native debugger that can be used to debug D applications.
Unfortunately, the Visual Studio Shell is missing one file, that is needed for the conversion of the debug information by cv2pdb. This is msobj80.dll for VS2008 and msobj100.dll for VS2010 and must be extracted from a standard installation, the Visual C Express edition or the Windows SDK. You might also find it installed by other Microsoft products.
Library search path not passed to linker
Even though Visual D allows to set a library search path, this does not work with the default installation of DMD. Optlink, the linker used by DMD, only accepts the path in the LIB environment variable (this is set by Visual D), but dmd overwrites it with the settings in its configuration file sc.ini.
You should change the LIB setting in <dmd-installation-path>\windows\bin\sc.ini to this:
LIB="%@P%\..\lib";\dm\lib;%DMD_LIB%
to pass through the value set by Visual D. Since version 0.3.14, DMD_LIB is used instead of LIB to avoid conflicts with the environment variable LIB being used by other compilers.