Enable waf acquisition and provide generic scripts (2/3) #1312
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
|
I think that having WAF support may be useful in the future, but until we have a library that is actively using it, I'd prefer to not merge this in. I'll close this for now, but we can reopen the PR in the future once we have a suitable user. Thanks! |
|
@ras0219-msft |
|
There are lots of waf use cases in LV2 (LADSPA v2) cross-platform audio plugin world:
I do automate builds that use waf for my Android libraries, but things are nasty and I am looking for any better approach to manage them. |
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.
This acquires waf and bootstraps it (compile waf executable). It also adds cmake scripts to simplify the creation of new waf-based portfiles. This is inspired by jom support ;)
This is the second PR in a row of interdependent PRs pkgconfig-waf->aubio.