-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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 gtsam #14339
add gtsam #14339
Conversation
Hi! This is the friendly automated conda-forge-linting service. I wanted to let you know that I linted all conda-recipes in your PR ( Here's what I've got... For recipes/gtsam:
For recipes/gtsam:
Documentation on acceptable licenses can be found here. |
Pulling your recipe @wolfv , in the tests looks like ceres-solver 2.0 release broke something:
|
Hi @ameysutavani I tried again, building against boost 1.76 (which will be the next conda-forge supported version). This won't be compatible with the RoboStack packages, but it's a start to get |
@wolfv Touch-basing on this thread again after a while; I tried solving the ceres autodiff.h issues that @venabled had pointed out here: #15578 The TL;DR status is:
A. Allow vendoring of GTSAM's 3rdparty ceres: The GTSAM user will need to be mindful that this may create conflicts with B. Wait for these dependencies to fixed upstream: This is probably not going to happen anytime soon. Would like to hear if there can be any more options that can be considered here from both @wolfv and @venabled ; |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).