digitalmars.D.ldc - New LDC user. Real stupid question.
- WhatMeWorry (22/22) Oct 18 2017 I'm not even out of the gate. Followed instructions at,
I'm not even out of the gate. Followed instructions at, https://wiki.dlang.org/Latest_LDC_binaries_for_Windows - Head over to the GitHub release and download the latest x64/x86 .7z artifact at the bottom. - Extract it somewhere. - Use the executables bin\ldc2.exe and/or bin\ldmd2.exe. Downloaded and extracted on windows 10 at c:\ldc\bin\... Created a tiny d program called GC.d in same directory. PS C:\LDC\bin> ldmd2 GC.d Error: cannot find source code for runtime library file 'object.d' ldc2 might not be correctly installed. Please check your ldc2.conf configuration file. Installation instructions can be found at http://wiki.dlang.org/LDC. import path[0] = C:\D\dmd2\windows\bin\..\include\d\ldc import path[1] = C:\D\dmd2\windows\bin\..\include\d I've looked at http://wiki.dlang.org/LDC and https://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC and don't seem to see a possible solution. What am I doing wrong? thanks.
Oct 18 2017
18.10.2017 21:18, WhatMeWorry пишет:I'm not even out of the gate. Followed instructions at, https://wiki.dlang.org/Latest_LDC_binaries_for_Windows - Head over to the GitHub release and download the latest x64/x86 .7z artifact at the bottom. - Extract it somewhere. - Use the executables bin\ldc2.exe and/or bin\ldmd2.exe. Downloaded and extracted on windows 10 at c:\ldc\bin\... Created a tiny d program called GC.d in same directory. PS C:\LDC\bin> ldmd2 GC.d Error: cannot find source code for runtime library file 'object.d' ldc2 might not be correctly installed. Please check your ldc2.conf configuration file. Installation instructions can be found at http://wiki.dlang.org/LDC. import path[0] = C:\D\dmd2\windows\bin\..\include\d\ldc import path[1] = C:\D\dmd2\windows\bin\..\include\d I've looked at http://wiki.dlang.org/LDC and https://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC and don't seem to see a possible solution. What am I doing wrong? thanks.it finds `include` folder next to `bin` one and fails. You should extract it too.
Oct 18 2017
On Wednesday, 18 October 2017 at 18:18:18 UTC, WhatMeWorry wrote:I'm not even out of the gate. Followed instructions at, https://wiki.dlang.org/Latest_LDC_binaries_for_Windows - Head over to the GitHub release and download the latest x64/x86 .7z artifact at the bottom. - Extract it somewhere. - Use the executables bin\ldc2.exe and/or bin\ldmd2.exe. Downloaded and extracted on windows 10 at c:\ldc\bin\... Created a tiny d program called GC.d in same directory. PS C:\LDC\bin> ldmd2 GC.d Error: cannot find source code for runtime library file 'object.d' ldc2 might not be correctly installed. Please check your ldc2.conf configuration file. Installation instructions can be found at http://wiki.dlang.org/LDC. import path[0] = C:\D\dmd2\windows\bin\..\include\d\ldc import path[1] = C:\D\dmd2\windows\bin\..\include\d I've looked at http://wiki.dlang.org/LDC and https://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC and don't seem to see a possible solution. What am I doing wrong? thanks.As I said on GitHub yesterday, you're better off with a normal release package from https://github.com/ldc-developers/ldc/releases. Anyway, your import paths are clearly wrong (no C:\LDC in there). I guess you extracted an LDC archive into C:\D\dmd2\windows and have C:\D\dmd2\windows\bin in your PATH, so that ldmd2 ends up invoking C:\D\dmd2\windows\bin\ldc2.exe or something like that. I suggest running ldmd2 with `-v` to check the binary and config file paths. The output should look similar to: binary C:\LDC\ninja-ldc\bin\ldc2.exe version 1.6.0git-366e2e4-dirty (DMD v2.076.1, LLVM 5.0.0git-64f4e71f1af) config C:\LDC\ninja-ldc\bin\ldc2.conf (x86_64-pc-windows-msvc) Otherwise, adapting your PATH environment variable should definitely get you working.
Oct 18 2017
On Wednesday, 18 October 2017 at 18:18:18 UTC, WhatMeWorry wrote:PS C:\LDC\bin> ldmd2 GC.dPS => PowerShell => need to use `./ldmd2` to start the executable from the current directory, just like on POSIX.
Oct 18 2017