-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
Set default compiler to be the same that built dub #303
Conversation
Seems like a good intermediate solution, I'll fix the help message. For the full solution I'd then go with something like #298 (keeping the original compiler as the default). |
Set default compiler to be the same that built dub
Actually, this has an issue: it defaults to the |
@Geod24: I've modified the code and the build scripts now to use the actual binary name that was used to build DUB. |
@s-ludwig It looks like this functionality has been lost. |
I didn't remember the history for this anymore, but it was removed deliberately: #678 But I'd say that #895 could be a good possibility to achieve the same practical outcome - assuming that that's the goal. It would probably make sense to implement that in conjunction with #875, for which I couldn't really make my mind up so far (any opinions on that one are very much appreciated). Another, possibly cleaner in terms of usual OS behavior, alternative would be to support a configuration file in the same directory as the dub executable, which could have a pre-filled |
One reason I can think of why it was removed is to be able to use an optimizing compiler (ldc/gdc) when building binaries of Dub for a release but that shouldn't affect the default chosen compiler when running Dub. |
Raising this PR as a bug - there are likely other things that need to change too, such as the help message.
" dmd (default), gdc, ldc, gdmd, ldmd"
It would be nice if the default compiler dub used was the same that built the application. So for me, I don't need to specify --compiler=gdc explicitly every time.