-
Notifications
You must be signed in to change notification settings - Fork 110
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
Fix cross-compile for Jetson Nano and PI Builds #3383
Conversation
FYI: I think the cross compiler worked as I checked the binary with the command |
However, when I ran I got this error message and I am not sure where that came from:
It could be I have not restart my laptop? |
Sometimes I see this if bazel isn't connected to the internet. Are you? |
Why are you running this? |
I just merged the two branch: this one, and Andrew's. Ansible seem to be able to flash. |
lmao. just realized I ran the wrong thing. This is what I ran: |
should we figure out why This playbook seems to be only ran once from the look of things. |
Forgot to mention, I flashed a robot successfully |
Please fill out the following before requesting review on this PR
Description
#3316 broke cross-compilation on Jetson Nano and Pi builds. It was using the host gcc compiler instead of the jetson nano compiler. This enables the required toolchain resolution flag that allows bazel to use the correct compiler.
Testing Done
Resolved Issues
Length Justification and Key Files to Review
Review Checklist
It is the reviewers responsibility to also make sure every item here has been covered
.h
file) should have a javadoc style comment at the start of them. For examples, see the functions defined inthunderbots/software/geom
. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class.TODO
(or similar) statements should either be completed or associated with a github issue