You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set CPM_USE_LOCAL_PACKAGES and call CPMAddPackage(...) for a local package, this path gets called, but after return() all the exported env variables are lost and are not available in the parent scope.
If you call CPMFindPackage(...), no status-like variables such as FOUND or ADDED are returned. It would be nice to maintain the same functionality as CPMAddPackage by returning those status variables.
I get warnings about CMP0144 when using CPM, can we set this policy?
The text was updated successfully, but these errors were encountered:
Bug
Set
CPM_USE_LOCAL_PACKAGES
and call CPMAddPackage(...) for a local package, this path gets called, but afterreturn()
all the exported env variables are lost and are not available in the parent scope.PROPAGATE is one way to address this.
Asks
FOUND
orADDED
are returned. It would be nice to maintain the same functionality as CPMAddPackage by returning those status variables.The text was updated successfully, but these errors were encountered: