-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build 2.068+ without binary downloads #17
Comments
At some point, building DMD will require a compiler newer than 2.067. Should Digger compile DMD three times in that case?
This risks subtly wrong builds if e.g. the wrong version is installed. If Digger is to achieve its goal of completely isolated and reproducible builds, it needs control over all dependencies. FWIW, the download will not occur if the ZIP file is placed in the /dl/ directory. |
As an option, yes. Automating bootstrapping feels to me one of major motivating points for usage of tools like Digger.
What about optionally defining it during compile-time? The thing is, I don't like to package things that silently download external binaries :) So some way to say "if you need DMD 2.067.0, just use system package" is very tempting path because I will maintain both in a lockstep. I am considering applying such distro-specific patch locally but wanted to hear your opinion first. |
cf1ae94 adds |
Awesome, thanks! Is it included in latest tagged release already? |
No, it will be part of the next release. On Wed, May 13, 2015 at 10:02 AM, Михаил Страшун notifications@github.com
|
Will make an Arch Linux package as soon as it is out in that case. |
Uploaded 2.2 beta. Will publish 2.2 in a week barring any issues. |
Curently Digger tries to download binary
2.066.1
release fromhttp://downloads.dlang.org/releases/2.x/2.066.1/dmd.2.066.1.zip
to build DMD version that requires host D compiler. It is preferrable to have an option to either build it locally or use a system-wide installation.The text was updated successfully, but these errors were encountered: