This is the home of a D compiler. SDC is at the moment, particularly stupid; it is a work in progress. Feel free to poke around, but don't expect it to compile your code.
The code is released under the MIT license (see the LICENCE file for more details). Contact me at firstname.lastname@example.org
SDC require DMD release
2.065 to compile.
Right now, SDC is a work in progress and unusable for any production work. It intends to provide a D compiler as a library (libd) in order to improve overall D toolchain by enabling the possibility of develloping new tools.
SDC now support many very advanced feature of (static ifs, string mixins, CTFE) but not many basic ones. This is a devellopement choice to allow the architecturing of the compiler around the hardest features of the language. As a consequence, SDC is a solid base to build upon.
See the tests directory for a sample of what is/should-be working. libs/object.d contains the current (temporary) object.d file for SDC.
This just me thinking outloud about what features I want, when.
- Compile D style (writeln) hello world.
- Compile itself, which imply compile most of D.
- Propose a stable API for 3rd party.
- extern (C++)
make and the latest DMD installed.
Install LLVM 3.3. Ensure that libd and libd-llvm provided as submodules are compiled properly.
Then you can compile
dmd and run it to run the test suites. There should be no regressions.
SDC contains le lot of hardcoded PATH right now, so it hard to integrate properly with the system. It expect object.d to be in ../libs/object.d
SDC require LLVM 3.3 . if the default llvm-config on your system is an older version, you can specify a newer version via
LLVM_CONFIG. For instance, on a debian system, you want to use
make LLVM_CONFIG=llvm-config-3.3 .
Extract the LLVM DLL binary archive to the SDC repository, then build with
make -f Makefile.windows.
When running SDC, make sure
opt are available in your PATH.
To run the tests, execute
dmd runner.d to build the test-runner application found in
tests/, then run it with