Does this msvc based build output gdb-compatible
debugging symbols?
No DWARFs in there.
And how do ldc and gdc do? =)
Thanks for the help with the Win64 version and for providing
the binary!
:) fwiw
A bunch of tests still crash.
I also have an experimental Win64 MSVC version.
https://github.com/Trass3r/ldc/releases
druntime:
make -f win64.mak DMD=../windows/bin/dmd.exe
CC=\c:\l\vc10\bin64\cl.exe\ target
phobos:
make -f win64.mak DMD=../windows/bin/dmd.exe
CC=\c:\l\vc10\bin64\cl.exe\ MAKE=c:\l\dmc\bin\make
AR=\c:/l/vc10/bin64/lib.exe\ LIB=..\lib64\phobos64.lib
That works?
So it probably doesn't need
Nope doesn't.
Setting VCDIR and SDKDIR via the make command works.
Setting VCDIR and SDKDIR via the make command works.
Works for me. Maybe you need a newer version of make (there was
a silent update in 2012, my version is 5.06).
Well if you don't set VCDIR you won't get proper include paths.
So no clue why it works for you.
The pdb debug format is not supported, AFAIK. But that format
is not documented and I don't think you could add D extensions
anyway.
So does LLVM really support PDB?
As long as they rely on the MS linker they only need to emit
proper debug info into the object files. But that's still TODO:
Digger is awesome. Have never heard of it before this talk.
Unfortunately it's a huge PITA to get a Win64 build with it cause
of those stupid hardcoded \Program Files (x86)\Microsoft Visual
Studio 10.0\VC paths. The modified makefiles etc are always
reverted by Digger before building.
You can add the compiler to the make command line with some
magic quoting.
My build script calls
druntime:
make -f win64.mak DMD=../windows/bin/dmd.exe
CC=\c:\l\vc10\bin64\cl.exe\ target
phobos:
make -f win64.mak DMD=../windows/bin/dmd.exe
CC=\c:\l\vc10\bin64\cl.exe\ MAKE=c:\l\dmc\bin\make
http://youtu.be/Es8st0E5428
Thx alot!
Enables me to watch it easily on my tv :)
http://youtu.be/n9RNxUQ0Cyk
12 matches
Mail list logo
