Difference between revisions of "Building and hacking LDC on Windows using MSVC"
Line 27: | Line 27: | ||
<ul> | <ul> | ||
+ | <li><tt>git clone http://llvm.org/git/llvm.git llvm</tt></li> | ||
<li><tt>md build-llvm-x64</tt></li> | <li><tt>md build-llvm-x64</tt></li> | ||
<li><tt>cd build-llvm-x64</tt></li> | <li><tt>cd build-llvm-x64</tt></li> | ||
− | |||
<li><p>Use a command like this:</p> | <li><p>Use a command like this:</p> | ||
<pre>cmake -G "Visual Studio 12 Win64" -DCMAKE_INSTALL_PREFIX="C:\Program Files\LLVM-x64" -DCMAKE_CXX_FLAGS="/DWIN32 /D_HAS_EXCEPTIONS=0 /MP /W3 /GR- /GS- /d2Zi+" | <pre>cmake -G "Visual Studio 12 Win64" -DCMAKE_INSTALL_PREFIX="C:\Program Files\LLVM-x64" -DCMAKE_CXX_FLAGS="/DWIN32 /D_HAS_EXCEPTIONS=0 /MP /W3 /GR- /GS- /d2Zi+" | ||
-DPYTHON_EXECUTABLE="C:\Program Files\Python33\python.exe" -DLLVM_TARGETS_TO_BUILD="X86" | -DPYTHON_EXECUTABLE="C:\Program Files\Python33\python.exe" -DLLVM_TARGETS_TO_BUILD="X86" | ||
− | -DLLVM_INCLUDE_TESTS=OFF -DLLVM_INCLUDE_EXAMPLES=OFF -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_APPEND_VC_REV=ON llvm</pre></li> | + | -DLLVM_INCLUDE_TESTS=OFF -DLLVM_INCLUDE_EXAMPLES=OFF -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_APPEND_VC_REV=ON ..\llvm</pre></li> |
</ul> | </ul> | ||
Line 64: | Line 64: | ||
<ul> | <ul> | ||
+ | <li><tt>git clone --recursive git://github.com/ldc-developers/ldc.git ldc</tt></li> | ||
<li><tt>md build-ldc2-x64</tt></li> | <li><tt>md build-ldc2-x64</tt></li> | ||
<li><tt>cd build-ldc2-x64</tt></li> | <li><tt>cd build-ldc2-x64</tt></li> | ||
− | |||
<li><p>Type the next command in one line:</p> | <li><p>Type the next command in one line:</p> | ||
<pre>cmake -G "Visual Studio 12 Win64" -DCMAKE_INSTALL_PREFIX="C:\Program Files\LDC" -DCMAKE_CXX_FLAGS="/DWIN32 /D_HAS_EXCEPTIONS=0 /MP /W2 /GR- /GS- /d2Zi+" | <pre>cmake -G "Visual Studio 12 Win64" -DCMAKE_INSTALL_PREFIX="C:\Program Files\LDC" -DCMAKE_CXX_FLAGS="/DWIN32 /D_HAS_EXCEPTIONS=0 /MP /W2 /GR- /GS- /d2Zi+" | ||
-DLLVM_ROOT_DIR="C:/Program Files/LLVM-x64" | -DLLVM_ROOT_DIR="C:/Program Files/LLVM-x64" | ||
-DLIBCONFIG++_INCLUDE_DIR="C:/ldcenv/libconfig-1.4.9/lib" | -DLIBCONFIG++_INCLUDE_DIR="C:/ldcenv/libconfig-1.4.9/lib" | ||
− | -DLIBCONFIG++_LIBRARY="C:/ldcenv/libconfig-1.4.9/Debug/libconfig++.lib" ldc</pre> | + | -DLIBCONFIG++_LIBRARY="C:/ldcenv/libconfig-1.4.9/Debug/libconfig++.lib" ..\ldc</pre> |
<p>This assumes that you have a static compiled version of <tt>libconfig++.lib</tt>. If you use the DLL version then you have to add <tt>-DLIBCONFIG_DLL=ON</tt>.</p></li> | <p>This assumes that you have a static compiled version of <tt>libconfig++.lib</tt>. If you use the DLL version then you have to add <tt>-DLIBCONFIG_DLL=ON</tt>.</p></li> | ||
</ul> | </ul> | ||
Line 78: | Line 78: | ||
Check that <tt>C:\Program Files\LDC\bin</tt> is in your path and type <tt>ldc2 -version</tt> to check that you can run <tt>LDC2</tt>. | Check that <tt>C:\Program Files\LDC\bin</tt> is in your path and type <tt>ldc2 -version</tt> to check that you can run <tt>LDC2</tt>. | ||
+ | |||
+ | === Running the tests === | ||
+ | |||
+ | The tests can currently NOT be run via <tt>msbuild RUN_TESTS.vcxproj</tt>. So we'll use a neat little build system called [http://martine.github.io/ninja/ Ninja] for this. | ||
+ | |||
+ | <ul> | ||
+ | <li>Download the latest Ninja release from [https://github.com/martine/ninja/releases GitHub] (a single .exe) and put it in your PATH.</li> | ||
+ | <li>Make sure you can link against the [http://wiki.dlang.org/Curl_on_Windows Curl] library (curl.lib in your LIB/LIBPATH, curl.dll in your PATH).</li> | ||
+ | <li>Run CMake just like when building LDC2, but use the <tt>Ninja</tt> generator this time: | ||
+ | <ul> | ||
+ | <li><tt>md ninja-ldc2-x64</tt></li> | ||
+ | <li><tt>cd ninja-ldc2-x64</tt></li> | ||
+ | <li><p>Type the next command in one line:</p> | ||
+ | <pre>cmake -G Ninja -DCMAKE_INSTALL_PREFIX="C:\Program Files\LDC" -DCMAKE_CXX_FLAGS="/DWIN32 /D_HAS_EXCEPTIONS=0 /MP /W2 /GR- /GS- /d2Zi+" | ||
+ | -DLLVM_ROOT_DIR="C:/Program Files/LLVM-x64" | ||
+ | -DLIBCONFIG++_INCLUDE_DIR="C:/ldcenv/libconfig-1.4.9/lib" | ||
+ | -DLIBCONFIG++_LIBRARY="C:/ldcenv/libconfig-1.4.9/Debug/libconfig++.lib" ..\ldc</pre> | ||
+ | </ul></li> | ||
+ | <li>Run the tests with <tt>ninja test</tt>. Grab a coffee, it could take a while. ;)</li> | ||
+ | </ul> | ||
+ | |||
+ | For troubleshooting be sure to examine the file <tt>ninja-ldc2-x64\Testing\Temporary\LastTest.log</tt>. | ||
=== Troubleshooting === | === Troubleshooting === | ||
Line 86: | Line 108: | ||
* Structured Exception Handling is only available for LLVM 3.6 head. Support has still alpha quality and is known to crash your application under certain circumstances. | * Structured Exception Handling is only available for LLVM 3.6 head. Support has still alpha quality and is known to crash your application under certain circumstances. | ||
− | |||
== Hacking druntime and phobos == | == Hacking druntime and phobos == |
Revision as of 20:03, 14 October 2014
LDC on Windows is work in progress. This page documents how to compile LDC2 on Windows 7 x64. It also provides hints on druntime and phobos.
Contents
Building LDC
Required software
- Windows 7 x64, of course!
- Install Visual Studio (e.g. Visual Studio 2013 Express for Windows)
- Python 2.7.x or Python 3.3.x (I use 3.3.0)
- git 1.8.x (I use 1.8.0.msysgit.0 installed with option "Run Git from the Windows Command Prompt")
- CMake 2.8.x (I use 2.8.12.1 installed with option "Add cmake to the system PATH for all users")
- a tool to extract .tgz files, e.g. 7-Zip
Required source downloads
- libconfig++ (Just use latest release 1.4.9.)
Environment check
After installing the software, you can open a "VS2013 x64 Native Tools Command Prompt". Running cmake --version should display the banner from cmake. Running git --version should display the banner from git. Running msbuild /version should display the banner from msbuild. Running <Python install path>\python --version should display the banner from python.
My working directory is C:\ldcenv. Every step starts in this directory. Please feel free to adjust this to your needs.
Build LLVM
To build LLVM from the command line, just execute the following steps:
- git clone http://llvm.org/git/llvm.git llvm
- md build-llvm-x64
- cd build-llvm-x64
Use a command like this:
cmake -G "Visual Studio 12 Win64" -DCMAKE_INSTALL_PREFIX="C:\Program Files\LLVM-x64" -DCMAKE_CXX_FLAGS="/DWIN32 /D_HAS_EXCEPTIONS=0 /MP /W3 /GR- /GS- /d2Zi+" -DPYTHON_EXECUTABLE="C:\Program Files\Python33\python.exe" -DLLVM_TARGETS_TO_BUILD="X86" -DLLVM_INCLUDE_TESTS=OFF -DLLVM_INCLUDE_EXAMPLES=OFF -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_APPEND_VC_REV=ON ..\llvm
Build the INSTALL project in the generated solution: msbuild INSTALL.vcxproj
The LLVM page on CMake documents other variables you can change. The most common is to add more targets. E.g. to build a target for ARM you change the targets to build to -DLLVM_TARGETS_TO_BUILD="X86;ARM".
Build libconfig++
Simple build instructions for libconfig++ are missing. You can do the following:
- Open the libconfig.sln solution
- Create a configuration for Win64 Debug
- If you like to create a static library then change the configuration type of project libconfig++ to 'Static library'.
- Build the project libconfig++
Alternative you can use a custom CMakeLists.txt:
- Extract libconfig++ file.
- Download CMakeLists.txt from this gist and place it into the root folder.
- Create a build directory: md build_libconfig
- cd build_libconfig
- Now create the build files:
- cmake ..\libconfig-1.4.9
- Build the library: msbuild ALL_BUILD.vcxproj
Build LDC2
To build LDC2 from the command line, just execute the following steps:
- git clone --recursive git://github.com/ldc-developers/ldc.git ldc
- md build-ldc2-x64
- cd build-ldc2-x64
Type the next command in one line:
cmake -G "Visual Studio 12 Win64" -DCMAKE_INSTALL_PREFIX="C:\Program Files\LDC" -DCMAKE_CXX_FLAGS="/DWIN32 /D_HAS_EXCEPTIONS=0 /MP /W2 /GR- /GS- /d2Zi+" -DLLVM_ROOT_DIR="C:/Program Files/LLVM-x64" -DLIBCONFIG++_INCLUDE_DIR="C:/ldcenv/libconfig-1.4.9/lib" -DLIBCONFIG++_LIBRARY="C:/ldcenv/libconfig-1.4.9/Debug/libconfig++.lib" ..\ldc
This assumes that you have a static compiled version of libconfig++.lib. If you use the DLL version then you have to add -DLIBCONFIG_DLL=ON.
Build the INSTALL project: msbuild INSTALL.vcxproj
Check that C:\Program Files\LDC\bin is in your path and type ldc2 -version to check that you can run LDC2.
Running the tests
The tests can currently NOT be run via msbuild RUN_TESTS.vcxproj. So we'll use a neat little build system called Ninja for this.
- Download the latest Ninja release from GitHub (a single .exe) and put it in your PATH.
- Make sure you can link against the Curl library (curl.lib in your LIB/LIBPATH, curl.dll in your PATH).
- Run CMake just like when building LDC2, but use the Ninja generator this time:
- md ninja-ldc2-x64
- cd ninja-ldc2-x64
Type the next command in one line:
cmake -G Ninja -DCMAKE_INSTALL_PREFIX="C:\Program Files\LDC" -DCMAKE_CXX_FLAGS="/DWIN32 /D_HAS_EXCEPTIONS=0 /MP /W2 /GR- /GS- /d2Zi+" -DLLVM_ROOT_DIR="C:/Program Files/LLVM-x64" -DLIBCONFIG++_INCLUDE_DIR="C:/ldcenv/libconfig-1.4.9/lib" -DLIBCONFIG++_LIBRARY="C:/ldcenv/libconfig-1.4.9/Debug/libconfig++.lib" ..\ldc
- Run the tests with ninja test. Grab a coffee, it could take a while. ;)
For troubleshooting be sure to examine the file ninja-ldc2-x64\Testing\Temporary\LastTest.log.
Troubleshooting
- git 1.7.11 requires extra setup because of git-svn. Just use 1.7.10 or 1.8.0.
Known bugs
- Structured Exception Handling is only available for LLVM 3.6 head. Support has still alpha quality and is known to crash your application under certain circumstances.
Hacking druntime and phobos
As of version 2.061 (still under development) Druntime and Phobos have support for Win64. The following issues are known:
- ldc.eh2: Implementation has alpha quality. Only used together with LLVM 3.4.
- Other missing functions: Most functions related to real type (long double in C) are missing because Visual C++ has dropped support for it (e.g. strtold(), sinl, cosl, ...). Some of them are already implemented (see e.g. std.math) but please be aware that there are still fake implementations present.
If you link your modules you have to specify the libraries phobos-ldc.lib and shell32.lib. Due to a bug in LLVM you have to specifiy the flag /LARGEADDRESSAWARE:NO, too.
Example
The simple D program hello.d
import std.stdio;
int main()
{
writefln("Hello LDC2");
return 0;
}
can be compiled and linked with the commands:
ldc2 -c hello.d link hello2.obj phobos-ldc.lib shell32.lib /LARGEADDRESSAWARE:NO
or simply with: ldc2 hello.d
The resulting hello.exe produces the expected output.