-
-
Notifications
You must be signed in to change notification settings - Fork 237
support specifying --d-versions #2646
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
Conversation
Usually you should prefer using configurations and build types, but sometimes, especially when wrapped in other build tools or when supporting e.g. different target platforms on the same target architecture and configuration, you may want to manually manage certain versions.
|
✅ PR OK, no changes in deprecations or warnings Total deprecations: 15 Total warnings: 0 Build statistics: statistics (-before, +after)
executable size=5284832 bin/dub
-rough build time=97s
+rough build time=96sFull build output |
|
Thank you Jan, this PR makes me happy. It also adds so much value to being able to add multiple additional version labels to dynamically add features, even to package maintainers. |
|
CI fails unrelated (happening on master all the time as well) |
PetarKirov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me - straightforward addition!
Usually you should prefer using configurations and build types, but sometimes, especially when wrapped in other build tools or when supporting e.g. different target platforms on the same target architecture and configuration, you may want to manually manage certain versions.