-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Make the library usable with FetchContent #382
Comments
Added a bounty of u$d 5 to the issue. |
Well, that was easy... the library is already usable with FetchContent. I just checked... |
Missing |
Yes, I'll add that.
That's to avoid any potential clashes with stuff within the library; although maybe it's not 100% necessary.
No, it's not... if you |
Nvm I tried to do |
Really? That's weird... Anyway, I'll have another look. |
So, I'm going to improve things! You will now be able to use the same namespace with find_package and with FetchContent! |
…proach * Adopt KitWare's Craig Scott's suggested approach to make CMake projects more compatible with use with `FetchContent`, as detailed [here](https://stackoverflow.com/a/72943178/1593077) (thanks goes to Alex Reinking). Now, projects using this library via `FetchContent` will also get the same namespaced target names as if they had used `find_package()`, plus there will now be much less chance of target name clashing. * Removing some less-useful comment text from `CMakeLists.txt` * Adjusting the `README.md` accordingly
…proach * Adopt KitWare's Craig Scott's suggested approach to make CMake projects more compatible with use with `FetchContent`, as detailed [here](https://stackoverflow.com/a/72943178/1593077) (thanks goes to Alex Reinking). Now, projects using this library via `FetchContent` will also get the same namespaced target names as if they had used `find_package()`, plus there will now be much less chance of target name clashing. * Removing some less-useful comment text from `CMakeLists.txt` * Adjusting the `README.md` accordingly
@eyalroz Please claim the bounty :) |
I could probably make the library usable with FetchContent, so that this would work:
The text was updated successfully, but these errors were encountered: