Open
Conversation
Owner
|
I don't know much about CMake but I feel like it's not in the spirit of single-file libraries as popularized by the stb libraries by Sean Barrett. Having such a build-system specific file in the repository would make it seem like that is a requirement. The beauty of single-file libraries is that anyone can integrate them the way it fits ones coding style. Be that with a complex build system or just compiling a single .c file via the command line. There is no recommended way how to integrate them because every way is valid :-) |
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
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 created a cmake buildfile that created build-targets for TinySoundFont. I am using this to allow the library dependency to be managed by vcpkg: https://github.com/Caldfir/vcpkg/tree/tinysf