-
Notifications
You must be signed in to change notification settings - Fork 789
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
ROS build farm are broken for develop branch #1967
Comments
You are correctly modeling my view: (3) if possible, (2) if not :-) |
SYSTEM was already there: so it will have to be (2)... |
What if we instead use a pragma in the problematic file to suppress that specific warning? That's probably a much cleaner solution and much more fine grained than using a pragma in an Eigen header and having it affect all downstream consumers. |
Mmm... Do you mean the embedded Eigen3's Do you agree with this change, Frank @dellaert ? |
Yes, that's the header I was referencing. Although I still think using pragmas in the affected gtsam files is a better method, mostly because of the granularity of control we get and the fact that it means we don't need to mess with Eigen. Also, it's likely that system Eigen packages would also be affected, so this solution would ensure that the warnings don't trigger on system Eigen packages as well. |
I agree with you, @Gold856 . If you have time for a small PR , please tag me so I can check it. If not I'll add it to my list... Key part: -Werror=maybe-uninitialized
PS: plus all other places including |
Description
See: https://build.ros2.org/job/Jdev__gtsam__ubuntu_noble_amd64/136/
Why?
Reason: the use of embedded Eigen version by default leads to not using the
SYSTEM
flag for those includes, so any warning there is treated as an error.Solutions
To modify CMake scripts so..
What do you think, @dellaert ?
I would like (1), but I know you like backwards compatible behavior, so the second choice would probably be (3), and if it's already done but is not working for some cmake limitation (cannot use SYSTEM for non-system directories? never checked that..), then use (2).
The text was updated successfully, but these errors were encountered: