The default compiler should not depend on DUB's own build environment #678
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Since we now have the generic |
|
BTW, I'll have a look at the user config now. |
s-ludwig
added a commit
that referenced
this pull request
Sep 13, 2015
A "defaultCompiler" field in the user or system wide DUB configuration file can be used for that now.
s-ludwig
added a commit
that referenced
this pull request
Sep 13, 2015
The default compiler should not depend on DUB's own build environment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When building DUB with
DMD=ldmd2 ./build.sh, the resultingdubbinary usesldmd2as default compiler at runtime. But IMO the behaviour ofdubat runtime should not depend on the environment it was built in.