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
Install bot2-lcmgl #6383
Install bot2-lcmgl #6383
Conversation
+@mwoehlke-kitware for feature review. High priority. FYI @fbudin69500. |
Reviewed 2 of 2 files at r1. tools/libbot.BUILD, line 150 at r1 (raw file):
BTW, why does this need to be split into a tools/libbot.BUILD, line 349 at r1 (raw file):
BTW, given how many sections there are (and how huge this file is), maybe tools/libbot.BUILD, line 420 at r1 (raw file):
BTW, should this be in tools/libbot.BUILD, line 527 at r1 (raw file):
BTW, did buildifier do this? Seems like the previous order was better... if this is buildifier's fault, we should add a custom tables (see bazelbuild/buildtools#45); not necessarily now, but at some point... Comments from Reviewable |
Review status: all files reviewed at latest revision, 3 unresolved discussions. tools/libbot.BUILD, line 150 at r1 (raw file): Previously, mwoehlke-kitware (Matthew Woehlke) wrote…
BTW This is a Bazel approximation of how upstream uses shell scripts. tools/libbot.BUILD, line 420 at r1 (raw file): Previously, mwoehlke-kitware (Matthew Woehlke) wrote…
BTW No see bot2_lcmgl_client above. Libbot does some ugly things, so it cannot be picked up by specifying a dep. tools/libbot.BUILD, line 527 at r1 (raw file): Previously, mwoehlke-kitware (Matthew Woehlke) wrote…
BTW It did. Comments from Reviewable |
+@jwnimmer-tri for platform review. |
Review status: all files reviewed at latest revision, 1 unresolved discussion. tools/libbot.BUILD, line 420 at r1 (raw file): Previously, jamiesnape (Jamie Snape) wrote…
BTW I'm confused; since Comments from Reviewable |
Review status: all files reviewed at latest revision, 1 unresolved discussion. tools/libbot.BUILD, line 420 at r1 (raw file): Previously, mwoehlke-kitware (Matthew Woehlke) wrote…
Libbot thing: Comments from Reviewable |
Review status: all files reviewed at latest revision, all discussions resolved. tools/libbot.BUILD, line 420 at r1 (raw file): Previously, jamiesnape (Jamie Snape) wrote…
Maybe I am unclear; I wasn't suggesting to rely on picking it up via a dep, I was asking what is wrong with it being three lines lower, in Comments from Reviewable |
Review status: all files reviewed at latest revision, 1 unresolved discussion. tools/libbot.BUILD, line 420 at r1 (raw file): Previously, mwoehlke-kitware (Matthew Woehlke) wrote…
To this package it is effectively private. Depends on your philosophy and whether you think the same header should be public for two different packages. Comments from Reviewable |
Review status: all files reviewed at latest revision, all discussions resolved. tools/libbot.BUILD, line 420 at r1 (raw file): Previously, jamiesnape (Jamie Snape) wrote…
OK Comments from Reviewable |
I guess once we've decided that Director needs to use Drake's build of libbot, then this is a necessary outcome. I'm not 100% why we're doing that, but I'll assume there's a good reason and just do a correctness review, rather dig into the appropriateness. Reviewed 2 of 2 files at r1. tools/libbot.BUILD, line 401 at r1 (raw file):
BTW Do we need this variable? It seems to duplicate the Comments from Reviewable |
tools/libbot.BUILD, line 401 at r1 (raw file): Previously, jwnimmer-tri (Jeremy Nimmer) wrote…
(Oops. The Comments from Reviewable |
Review status: all files reviewed at latest revision, 1 unresolved discussion. tools/libbot.BUILD, line 401 at r1 (raw file): Previously, jwnimmer-tri (Jeremy Nimmer) wrote…
The LCM types cause the issue. You end up with them being installed twice into two different locations if you use Comments from Reviewable |
Apparently Director needs this.
This change is