Switch to rattler-build

[h-vetinari]

This PR is not immediately meant for merging, but for doing a logical separation of different changes on the way to exploratory emscripten support. Builds on #82

Still needs a bunch of fixes in our infra.

[conda-forge-webservices]

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 (recipe/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

This is a rattler-build recipe and not yet lintable. We are working on it!

[h-vetinari]

There's a subtle behaviour change in how %LIBRARY_LIB% existed during the global build stage before, but doesn't anymore. No big deal, but triggered a failed copy here, c.f. 70e47af

[conda-forge-webservices]

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 (recipe/recipe.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

This is a v1 recipe and not yet lintable. We are working on it!

[wolfv]

I've re-triggered some builds to see if rattler-build 0.22.0 changes anything :)

[h-vetinari]

Interesting - on windows, cmake doesn't seem to be found; it's definitely there though, and also works before the translation to RB.

 │ │ Resolving build environment:
 │ │   Platform: win-64 [__win=0=0, __archspec=1=x86_64_v4]
 │ │   Channels: 
 │ │    - file:///D:/bld/
 │ │    - conda-forge
 │ │   Specs:
 │ │    - cmake
 │ │    - ninja
 │ │    - vs2019_win-64
 │ │    - vs_win-64
 │ │ [...]
 │ │ 'cmake' is not recognized as an internal or external command,
 │ │ operable program or batch file.

[wolfv]

We can see that the osx version is detected as 10.16 now, too:

 │ │ Resolving host environment:
 │ │   Platform: osx-64 [__unix=0=0, __osx=10.16=0, __archspec=1=skylake]
 │ │   Channels: 
 │ │    - file:///Users/runner/miniforge3/conda-bld/
 │ │    - conda-forge
 │ │   Specs:
 │ │    - __osx >=11.0

Which breaks the tests, since they require 11.0.

[wolfv]

Strange because jolt-physics seems fine (also CMake) conda-forge/jolt-physics-feedstock#3

[h-vetinari]

Strange because jolt-physics seems fine (also CMake) conda-forge/jolt-physics-feedstock#3

Perhaps another little 🐞 hiding in cache:? 🤔

[h-vetinari]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you but ran into some issues. Please check the output logs of the GitHub actions workflow below for more details. You can also ping conda-forge/core for further assistance or you can try [rerendering locally](https://conda-forge.org/docs/maintainer/updating_pkgs.html#rerendering-with-conda-smithy-locally.

The following suggestions might help debug any issues:

• Is the recipe/{meta.yaml,recipe.yaml} file valid?
• If there is a recipe/conda-build-config.yaml file in the feedstock make sure that it is compatible with the current global pinnnings.
• Is the fork used for this PR on an organization or user GitHub account? Automated rerendering via the webservices admin bot only works for user GitHub accounts.

_{This message was generated by GitHub actions workflow run https://github.com/conda-forge-webservices/actions/runs/11139428595.}

[h-vetinari]

FYI @wolfv @beckermr
The admin bot didn't manage to rerender here, but manually it worked (modulo changes necessary for conda-forge/conda-smithy#2057)

[conda-forge-admin]

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 (recipe/recipe.yaml) and found some lint.

Here's what I've got...

For recipe/recipe.yaml:

• ❌ The top level meta key cache is unexpected

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12372865903. Examine the logs at this URL for more detail.}

[h-vetinari]

but manually it worked

Nevermind, that's almost certainly because I monkey-patched my local install (xref prefix-dev/rattler-build-conda-compat#56).

[h-vetinari]

@wolfv, cmake isn't found in any of the builds -- at least now the error is consistent across platforms I guess 😅

Looks like a cache: problem to me. Do you want me to open an issue in rattler-build?

[wolfv]

An issue with a small reproducer would be great :)

[h-vetinari]

I'll try to switch to the package_content tests, but regardless of how much can be converted, having no output for

test:
  commands:
    - ...

is a complete dealbreaker from my POV. I don't even see the inconsistency you mentioned with other script executions (well, those that are defined in a yaml list at least) - in those cases it's equally important to know which line failed.

[wolfv]

Definitely! If you have a simple repro I can debug or can come up with something myself