[question] Yocto SDK together with conan2?

[mickeyproc]

What is your question?

Hi! I have a question regarding Yocto together with Conan2.
I know you have an integration wiki for conan v1 when it comes to Yocto, but i cannot figure out how to get it to work with conan v2.

I've build a Yocto SDK (Scarthgap release) that I install on my linux machine (Ubuntu 24.04). I then use conan2 to get thirdparty packages (Boost 1.86.0 and OpenCV 4.10.0) to build applications together with the SDK for my arm64 target (imx8).

The conanfile.py is very simple:

from conan import ConanFile
from conan.tools.cmake import cmake_layout

class ExampleRecipe(ConanFile):
    settings = "os", "compiler", "build_type", "arch"
    generators = "CMakeDeps", "CMakeToolchain"

    def requirements(self):
        self.requires("opencv/4.10.0")
        self.requires("boost/1.86.0")

    def layout(self):
        cmake_layout(self)

And my profile called yocto:

[settings]
os=Linux
arch=armv8
compiler=gcc
compiler.version=11
compiler.libcxx=libstdc++11
build_type=Release

[buildenv]
SYSROOT=/home/mic/mysdk/1.0.0/sysroots/cortexa53-crypto-hw-linux

And then i try do install packages with conan:

#!/bin/bash
source /home/mic/mysdk/1.0.0/environment-setup-aarch64-poky-linux
python3 -m venv py-dev-env
source ./py-dev-env/bin/activate
pip3 install -r requirements.txt # Just conan

# conan stuff
CONAN_HOME=$(pwd)/.conan2
export CONAN_HOME
conan profile detect --force

# Need some conan pkg/system packages
PKG_CONFIG_PATH="/usr/lib/x86_64-linux-gnu/pkgconfig/:/usr/share/pkgconfig/:${PKG_CONFIG_PATH}"
export PKG_CONFIG_PATH
mkdir -p build && cd build
conan install .. --build=missing  --profile=yocto

Am i missing something in the conan profile?
I am happy to contribute to the wiki when i got it working.

Have you read the CONTRIBUTING guide?

• I've read the CONTRIBUTING guide

UPDATE:
I can see there is already some pages in this area at #7285 and #14343
But i am still unable to build with yocto SDK. I feel like it something pretty small that i just haven't figured out.

[memsharded]

Hi @mickeyproc

Thanks for your question.

There could be different aspects here. One of them is that the build system or recipes for some of those packages such as boost or opencv might not be that ready for cross-compilation, or require some special configuration.

Another possibility would be that there is something missing in the Yocto integration for Conan, it is true that we didn't have time enough to properly update and document everything for Conan 2.

To differentiate among those scenarios I'd recommend to start with a simpler dependency. The conan new cmake_lib -d name=mypkg -d version=0.1 will create a simple CMake template based Conan package, that can be easily created. You can for example conan export . it, and that will put it in the cache available for your yocto consumer project, so you can self.requires("mypkg/0.1") it instead of opencv or boost.

I'll also try to push to get the basic docs for Yocto in Conan 2 docs.

[uilianries]

@mickeyproc Hello!

The project meta-conan offers the branch conan2/scarthgap with support for Conan 2.x, just like it was working with Conan 1.x, but respecting the profiles.

I just tried to build Boost meta-conan and worked: /home/uilian/Development/yocto/poky/meta-conan/conan-boost-build.log

There is no documentation for Conan 2.x and Yocto (yet), but you can used the previous document as reference when consuming a package: https://docs.conan.io/1/integrations/cross_platform/yocto.html#write-the-bitbake-recipe-for-the-conan-package

Please, comment if using meta-conan works for your case.