Fixed incorrect INSTALL_INTERFACE #138
Open
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
adamkewley
force-pushed
the
fix_bad-install-interface
branch
from
4081fa0
to
e4887bf
Compare
|
(force-updated with a version that worked when clean-building OSC: my aim with the branch is to provide a single commit that i can |
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.
Related #132
I'm using lunasvg in opensim-creator, which is a cross-platform app for Linux, Mac, and Windows.
Lunasvg works great, but I am finding (similar to #132) that the installed CMake target cannot locate the installed header files etc.. I generally have to patch each lunasvg with this changeset in order to get things working on my target platforms.
I don't know if this is the best approach for it--this is just a suggestion--and I don't have any expectations w.r.t. changes, timelines, etc. - this is just an idea that would be handy for me if considered, because it would mean I don't need to manually add this changeset to each lunasvg release whenever I get around to updating my dependencies.