add libcamera and related recipes

[carlodri]

https://libcamera.org/index.html

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[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 (recipes/libcamera/meta.yaml) and found some lint.

Here's what I've got...

For recipes/libcamera/meta.yaml:

• ❌ This recipe is using a compiler, which now requires adding a build dependence on {{ stdlib("c") }} as well. Note that this rule applies to each output of the recipe using a compiler. For further details, please see META: {{ stdlib("c") }} migration conda-forge.github.io#2102.

For recipes/libcamera/meta.yaml:

• ℹ️ The boost-cpp output has been superseded by libboost-devel (as of 1.82), which now comes with a run-export (on libboost) as well. In case you only needed the boost headers, you should use libboost-headers.

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

[conda-forge-admin]

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

[carlodri]

@conda-forge/help-c-cpp can someone help me in landing this? I think this a pretty relevant library. But my c-cpp skills are too low to get it working....

This is also important to have the picamera2 Python library built in a flexible way and still maintaining the strict link required between the versions of picamera2-libcamera. As soon as libcamera works I would like to add it here to the same feedstock.

[carlodri]

CC @hmaarrfk sorry to ping you on this but I had the feeling that you could also be interested. Forgive me if not...

[carlodri]

@conda-forge-admin please rerender

[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 (recipes/libcamera/meta.yaml) and found some lint.

Here's what I've got...

For recipes/libcamera/meta.yaml:

• ❌ You are setting c_stdlib_version below the current global baseline in conda-forge (10.13). If this is your intention, you also need to override MACOSX_DEPLOYMENT_TARGET (with the same value) locally.

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

[hmaarrfk]

if you don't personally need osx support, then don't worry about it. let somebody else come in and help you with it "later".

Now you should still move your dependencies to the host section, keep tools like pkg-config, meson, cmake, compilers in the build section.

[carlodri]

at the moment I only need aarch64. Am I understanding your suggestion correctly, to drop the aarch_64 for now, build only on linux_64 and then migrate later?

[hmaarrfk]

at the moment I only need aarch64. Am I understanding your suggestion correctly, to drop the aarch_64 for now, build only on linux_64 and then migrate later?

yes. mostly doing cross compilation blind is sure to fail.... especially if you are having trouble organizing the dependencies correctly.

You can just ask the bot to rerender immeimdately and it gives you a PR that you can edit.

[conda-forge-admin]

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 (recipes/libcamera-rpi/meta.yaml, recipes/libcamera/meta.yaml) and found it was in an excellent condition.

[carlodri]

at the moment I only need aarch64. Am I understanding your suggestion correctly, to drop the aarch_64 for now, build only on linux_64 and then migrate later?

yes. mostly doing cross compilation blind is sure to fail.... especially if you are having trouble organizing the dependencies correctly.

You can just ask the bot to rerender immeimdately and it gives you a PR that you can edit.

thanks a lot for the insight and help @hmaarrfk, trying now on linux_64 only.

[hmaarrfk]

There is always something odd with meson stuff.

Basically, meson pulls in python, and then the build python gets found.... if python is actually a build time dpenednecy, then we can move all the python stuff to the build prefix.

But hte "libraries", like libjpegturbo should be in the host section for sure.

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!

[carlodri]

sorry pinged the staged recipes team by mistake, this is not ready yet

[carlodri]

@hmaarrfk what do you think? I'm not sure about the libcamera-rpi lacking tests. And maybe we could merge this one before adding https://github.com/raspberrypi/picamera2

Let me know your thoughts (and if you want to help maintain this mess I made 😅)

[hmaarrfk]

you can likely add test for existance of headers and so files.

[hmaarrfk]

are header files and so files expected? if so, add those tests.

[hmaarrfk]

See tensorflow or PyTorch for recipes with variants. They have selectors in the meta.yaml. You would have a selector for the source url and the source sha256

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent but I have some suggestions.

File-specific lints and/or hints:

• recipes/libcamera/meta.yaml:
  • hints:
    • It looks like you are submitting a multi-output recipe. In these cases, the correct name for the feedstock is ambiguous, and our infrastructure defaults to the top-level package.name field. Please add a feedstock-name entry in the extra section.

[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 (recipes/libcamera/meta.yaml) and found some lint.

Here's what I've got...

For recipes/libcamera/meta.yaml:

• ❌ The "source" section was expected to be a dictionary or a list, but got a builtins.NoneType.
• ❌ Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [66, 75]
• ❌ The recipe is not parsable by any of the known recipe parsers (['conda-forge-tick (the bot)', 'conda-recipe-manager', 'conda-souschef (grayskull)']). Please check the logs for more information and ensure your recipe can be parsed.
• ❌ The "source" section was expected to be a dictionary or a list, but got a builtins.NoneType.

For recipes/libcamera/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-forge-tick (the bot). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

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

[conda-forge-admin]

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

[hmaarrfk]

don't bother creating different pakcage names, just different build strings.

that will make them exclusive.