-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add build file for suitesparse's CHOLMOD / SPQR [OC-310] #109
Conversation
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.
You should be able to run bazel run //:buildifier
to format the code.
ee12e8c
to
fcdaa64
Compare
cc @isaactorz |
There was some discussion here that moved to slack but the gist of it is we'll need to update our sysroot to include the new dependencies on Matt's switched to a different task temporarily though. |
Thanks for the update. |
I'm going to remove the review request for now |
This is required for the sparse householder QR changes in swift-nav/orion-engine#7126 swift-nav/rules_swiftnav#109 swift-nav/albatross#453 swift-nav/cmake#167
third_party/suitesparse.BUILD
Outdated
@@ -300,6 +312,8 @@ cc_library( | |||
"CHOLMOD/SuiteSparse_metis/include/", | |||
], | |||
linkopts = [ | |||
"-Lexternal/aarch64-sysroot/usr/lib/aarch64-linux-gnu/lapack", |
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 thought about this a little more and we're probably going to need to guard these in a select
statement so that they're only put on the link line when we're actually using the sysroot.
The way bazel's build tree is structured - the external/aarch64-sysroot/
folder may be on the path even when not doing a build against a sysroot. This could cause the build to attempt to link libs for the wrong platform.
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've added the appropriate guards.
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.
Thanks.
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.
LGTM assuming all testing goes well!
5e6ab60
to
b6e2417
Compare
I've updated to your version of this PR (with
|
OK, false alarm -- your branch did not update the sysroot pointer. I think it should be OK now. |
No description provided.