-
Notifications
You must be signed in to change notification settings - Fork 202
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
Minor cmake clean up pxr plugin #653
Conversation
…rings in the dependencies for usd and maya libraries.
@@ -26,7 +25,6 @@ pxr_shared_library(${PXR_PACKAGE} | |||
mayaUsd | |||
|
|||
INCLUDE_DIRS | |||
${Boost_INCLUDE_DIRS} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these variables are empty?? The mystery part is how usdMaya links against Boost?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some cleanup is definitely warranted here since so much has moved out of these components, but I don't really agree with stripping it down to just mayaUsd
. That may be part of what creates mysteries about where link dependencies are coming from when they come in transitively.
If an upstream library is included and used directly by a downstream library, the downstream library should explicitly declare that dependency.
Respectfully, I have a different view on this. Explicitly declaring upstream library again in the downstream library is totally redundant. If upstream library is properly using PRIVATE/PUBLIC/INTERFACE keywords, one can look up the upstream dependencies to find out what they are. For example, mayaUsdUtils is declaring gf, usd, sdf as PUBLIC. The downstream library DiffCore doesn't really need to repeat them again. mayaUsdUtils maya-usd/lib/usd/utils/CMakeLists.txt Line 42 in 461668a
DiffCore
I am happy to revert the change if you still disagree. The important change in this PR is getting rid of those empty boost entries. They are very confusing and Sean and I were wondering how usdMaya builds without them. That's the real mystery :) |
Fair enough. I definitely see your point, and if the only reason that we were declaring that In the case here though, Consider the case where in some future change, for whatever reason we decide to remove all usage of So I'd still contend that many of these declared dependencies should remain here (basically any library that is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking as reviewed...
@mattyjams Thanks for the explanation. It makes sense to me now. I removed plug as you suggested but put back everything else. See 114c4ec |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, thanks @HamedSabri-adsk! A few other now unused libraries could get yanked if you want, but otherwise looks good to me!
gf | ||
js | ||
kind | ||
plug | ||
sdf | ||
tf | ||
usd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Of the libraries still listed here, it looks like you could now also remove these if you wanted to:
js
usdLux
usdRi
usdShade
usdSkel
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. Please see f70e798
No description provided.