-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 recipe for labmaze #21512
Add recipe for labmaze #21512
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 ( |
The windows build fails with:
Perhaps we need to stop the bazel daemon after starting it? |
Windows is failing with:
macOS with:
macOS probably can be fixed either by passing |
Directly linking the python libraries resulted in a segfault for some reason, let's switch to pass |
The Windows problem was fixed by specifying to pip to use a temporary directory inside the working dir. |
@conda-forge/help-c-cpp the recipe is ready for review. As I am not expert in bazel I am not sure if I did everything fine from the bazel point of view, so this may be interesting also for @conda-forge/bazel . |
recipes/labmaze/meta.yaml
Outdated
{% set version = "1.0.6" %} | ||
|
||
package: | ||
name: {{ name }} | ||
version: {{ version }} | ||
|
||
source: | ||
url: https://github.com/deepmind/labmaze/archive/6d7e8f058428025cd4253f1ef6a1ed6618d9b0ea.zip | ||
sha256: dbd3e0b96e1b50936846bdc6f8f63d1199ca6319aefa64c0f5c9a5d29858f605 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the recipe to be more clear in 0c0c674 .
recipes/labmaze/meta.yaml
Outdated
host: | ||
- pybind11 | ||
- pybind11-abi | ||
- abseil-cpp |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's linking warnings about libabseil. Are you accidentally static linking?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be:
- abseil-cpp | |
- libabseil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's linking warnings about libabseil. Are you accidentally static linking?
I am using just an header-only part of abseil. I added an ignore of libabseil's run_exports in d85e453 to account for that.
recipes/labmaze/unvendor_deps.patch
Outdated
+ path = "/home/traversaro/mambaforge/envs/labmazedev/include", # absl placeholder | ||
+ build_file = "@//bazel:system_absl.BUILD" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can this local path work in CI, or is this simply never built...?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is replaced by setup.py, following the structure already used in the recipe for the python headers, however given that a random local path was confusing, I substituted it with a clearly fake path in 2a405c0 .
Co-authored-by: h-vetinari <[email protected]>
@h-vetinari @carterbox thanks a lot for the comments, I tried to address them, once the review is completed I will stash the commits because ~35 are quite a lot. |
Checklist
url
) rather than a repo (e.g.git_url
) is used in your recipe (see here for more details).