-
-
Notifications
You must be signed in to change notification settings - Fork 365
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
Handle _CROW_ILL or _CROW_ICD being NOTFOUND #720
Conversation
If the variable is NOTFOUND then set it to "". Then at the end after possible list appends. If the variable is not "" then update the target properties. This gets rid of a warning
Fixes #661 |
For those who want the patch for the latest release v1.0+5 |
Any updates on this? |
The fix works for me. Lmk if there is an issue with anything. |
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.
Have a look at the proposed simplified version.
Hi gittiver, thank you for the feed back! We cannot follow through with those two changes. For the first one. We need to set it to For the second one, we still need to check if empty because in another project I found if you try to add |
I will have a look on the complete cmake files, I had just reviewed the changes. |
Any update on this? The library is not usable in its current state:
|
lets go with your solution. |
Anyone looking for a workaround to use prior to the release can be found in a comment in the accompanying issue: |
There is a big warning that may appear when compiling user code:
When using
get_target_property
in cmake and the property is not found it will define the content of the variable<var>-NOTFOUND
and because these variables were being used as compile definitions it causes a bunch of warnings due to the-
in the name.Solution:
If the variable is
NOTFOUND
then set it to""
. Then at the end after possible list appends. If the variable is not""
then update the target properties. This means we do not add the compile definition at all.This gets rid of a warning. And since there is nowhere in the code looking for NOTFOUND it does not change functionality.