Skip to content
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

drake_bazel_external vs commercial solvers #108

Open
jwnimmer-tri opened this issue Jun 14, 2018 · 3 comments
Open

drake_bazel_external vs commercial solvers #108

jwnimmer-tri opened this issue Jun 14, 2018 · 3 comments

Comments

@jwnimmer-tri
Copy link
Contributor

The drake_bazel_external documentation doesn't give any hint about how to turn on the commercial solvers for mathematical programs (SNOPT, MOSEK, Gurobi) when using Drake as a Bazel external. We should document it.

@jwnimmer-tri
Copy link
Contributor Author

The easy answer to recommend is that in the downstream tools/bazel.rc file within their project, to add something like this:

# Enable Gurobi by default.
build --define=WITH_GUROBI=ON

Maybe just some commented-out lines in our example drake_bazel_external/tools/bazel.rc would be good enough.

@EricCousineau-TRI EricCousineau-TRI self-assigned this Jun 14, 2018
@pvarin
Copy link

pvarin commented Jun 16, 2018

It might also make sense to mention that we need to add the license file environment variable to allow tests to work

test --test_env=GRB_LICENSE_FILE

@jamiesnape
Copy link
Contributor

The drake_bazel_external documentation doesn't give any hint about how to turn on the commercial solvers for mathematical programs (SNOPT, MOSEK, Gurobi) when using Drake as a Bazel external. We should document it.

Indeed. It was, of course, a deliberate omission originally, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants