Note: This website is archived. For up-to-date information about D projects and development, please visit wiki.dlang.org.

Changes between Version 13 and Version 14 of Installation

Show
Ignore:
Author:
sagitario (IP: 217.232.79.108)
Timestamp:
05/28/13 06:05:31 (6 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Installation

    v13 v14  
    5252 
    5353A '''free''' alternative are the integrated '''Visual Studio Shell''' distributions, that can be downloaded 
    54 here: ([http://www.microsoft.com/downloads/details.aspx?FamilyID=40646580-97FA-4698-B65F-620D4B4B1ED7&displaylang=en VS Shell 2008] 
    55 and [http://www.microsoft.com/downloads/details.aspx?FamilyID=8e5aa7b6-8436-43f0-b778-00c3bca733d3&displaylang=en VS Shell 2010]). 
    56 The shells are identical with the Visual Studio IDE, but stripped of any language support. It 
     54here: ([http://www.microsoft.com/downloads/details.aspx?FamilyID=40646580-97FA-4698-B65F-620D4B4B1ED7&displaylang=en VS Shell 2008], 
     55[http://www.microsoft.com/downloads/details.aspx?FamilyID=8e5aa7b6-8436-43f0-b778-00c3bca733d3&displaylang=en VS Shell 2010]) and VS Shell 2012 (see below for links). The shells are identical with the Visual Studio IDE, but stripped of any language support. It 
    5756still contains the native debugger that can be used to debug D applications. 
    5857 
    5958For debugging applications, you should also install cv2pdb which is now included in the 
    6059Visual D installer. Please make sure, changes to Common7\Packages\Debugger\autoexp.dat do 
    61 not mix with previous manual installations of [http://svn.dsource.org/projects/cv2pdb cv2pdb]. 
     60not mix with previous manual installations of [http://svn.dsource.org/projects/cv2pdb cv2pdb]. Visual D also installs the alternative debug engine mago that does not need cv2pdb. 
    6261 
    63 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. 
     62Unfortunately, the Visual Studio Shells 2008 and 2010 are 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. 
    6463Put this file alongside mspdbcore.dll, normally in <VS-installation-path>\Common7\IDE. 
     64 
     65The Visual Studio Shell 2012 is installed with two packages, the [http://www.microsoft.com/en-us/download/details.aspx?id=30670 isolated shell] followed by the [http://www.microsoft.com/en-us/download/details.aspx?id=30663 integrated package]. Fortunately it 
     66has all the files needed for debugging, and the Visual D installer patches the installation to make the x64 debugger work. 
    6567 
    6668= Using GDC = 
    7173 * GDC binaries: https://bitbucket.org/goshawk/gdc/downloads 
    7274 
    73 Add the MinGW64/bin path to your PATH environment variable or the executable path list in the "Visual D Directories" option page. Then switch the "Compiler" option in the project configuration to "GDC". 
     75Add the MinGW64/bin path to your PATH environment variable or the executable path list in the "GDC Directories" option page. Then switch the "Compiler" option in the project configuration to "GDC". 
    7476 
    7577To create a 64-bit executable, you will have to add a new platform to the project and solution in the configuration manager.