Add support for --with and --without flags
#20
Merged
Conversation
This file contains 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
|
Hi, thank you for the contribution! I haven't looked at it in detail yet, but I will probably merge it since there is not much increase in code. I am planning to release 3.0 in the near future, and will include it there. Please wait a little longer. |
|
Sorry for the delay. I have merged this. I will be releasing v3.0.0 in the next few days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have added expansion for
--with{out}-*flags, which can be useful in certain areas, such asconfigurescripts. It essentially works exactly the same as the expansion of--{no-}*flags.I have updated some of the unit tests, although I am not certain whether more are needed. What do you think about this change?