Add spot-cpp-sdk - #32887
Conversation
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Hi! This is the staged-recipes linter and your PR looks excellent! 🚀 |
|
The I guess I need to add a run eigen dependency in addition to the abi package. Note that this package is case B. If the library contained in the recipe includes Eigen headers (either directly or indirectly) in public headers and it has not a |
|
Looping @traversaro in for an early feedback on how to handle eigen here. I'd like to merge this with |
|
Given that this is a new package, if you want to make sure that |
|
Windows is currently failing due to the following error I have no idea how to fix this, trying a Gemini suggestion using a injected header 5a7bc27. |
|
I attempted to implement a workaround for the Windows build errors but found no sustainable solution. After failing to resolve the core compilation issues (macro collisions), I tried disabling the problematic choreography protos and their cascading dependencies. However, this resulted in a severely stripped-down API that would offer little value to users. Considering the high maintenance cost of these fragile patches and the fact that likely the windows user base will be small compared to linux, I am disabling windows support entirely. I encourage any interested contributors with access to a windows development environment to refine the recipe directly in the feedstock repository. |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipes/spot-cpp-sdk/recipe.yaml:
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/24210333096. Examine the logs at this URL for more detail. |
|
I introduced a new On the long term (as soon as conda/ceps#102 is accepted), I believe the recipe can be further improved by moving headers and I am facing the following problem when I try to implement the documented Eigen pattern for recipes with |
|
@conda-forge/help-c-cpp any guidance on how to address this problem the intended way? |
|
@conda-forge/help-c-cpp, ready for review! |
| - ninja | ||
| host: | ||
| - cli11 | ||
| - eigen-abi-devel <5 |
There was a problem hiding this comment.
Any specific reason for the <5 constraint? The build should get the 3.4.0 constraint from the pinnings, and then the migrator bot should open a PR to update the version.
There was a problem hiding this comment.
Nope I haven't tried without the pin, I expected v5 to be already the default and I wanted to prevent it. Let me try.
There was a problem hiding this comment.
Done in 2c06c7e, I confirm that eigen<5 is still the default
│ Finalized run dependencies (spot-cpp-sdk-5.1.4-he70b258_0):
│ ╭──────────────────┬────────────────────────────────────────────────────────────╮
│ │ Name ┆ Spec │
│ ╞══════════════════╪════════════════════════════════════════════════════════════╡
│ │ Run dependencies ┆ │
│ │ __glibc ┆ >=2.17,<3.0.a0 (RE of [build: sysroot_linux-64]) │
│ │ eigen-abi ┆ >=3.4.0.100,<3.4.0.101.0a0 (RE of [host: eigen-abi-devel]) │
│ │ libabseil ┆ >=20250512.1,<20250513.0a0 (RE of [host: libabseil]) │
│ │ ┆ * cxx17* (RE of [host: libabseil]) │
│ │ libgcc ┆ >=14 (RE of [build: gxx_linux-64]) │
│ │ ┆ >=14 (RE of [build: gcc_linux-64]) │
│ │ libgrpc ┆ >=1.73.1,<1.74.0a0 (RE of [host: libgrpc]) │
│ │ libprotobuf ┆ >=6.31.1,<6.31.2.0a0 (RE of [host: libprotobuf]) │
│ │ libstdcxx ┆ >=14 (RE of [build: gxx_linux-64]) │
│ ╰──────────────────┴────────────────────────────────────────────────────────────╯
|
@traversaro I addressed your comments |
Since it pins exactly the subpackage, the transitive run_exports of eigen-abi should suffice
2c06c7e to
1ff09ea
Compare
|
Thanks! |
|
Thanks @traversaro for merging! This time something went wrong with the automatic creation of the feedstock, I see an empty repo. What could be done when this happens? |
|
Got finally populated, problem solved. |
Project repo: https://github.com/boston-dynamics/spot-cpp-sdk
Develop applications and payloads for Spot using the Boston Dynamics Spot C++ SDK.
Checklist
url) rather than a repo (e.g.git_url) is used in your recipe (see here for more details).