Skip to content
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

[Kirkstone] cross dependency with meta-rust and meta-lts-mixins #805

Open
davidcodesido opened this issue May 3, 2024 · 16 comments
Open

Comments

@davidcodesido
Copy link

I'm currently building a project that requires azure-iotedge which depends on meta-rust and chromium. The project is based on kirkstone thus it needs meta-lts-mixins to provide rust according to the documentation.

Is there any way I can combine both dependecies? I'm quite new to yocto/rust/cargo etc. Any help is welcome.

@davidcodesido davidcodesido changed the title cross dependency with meta-rust and meta-lts-mixins [Kirkstone] cross dependency with meta-rust and meta-lts-mixins May 3, 2024
@kraj
Copy link
Collaborator

kraj commented May 3, 2024

we only support master branch across releases so best option is to try master branch

@davidcodesido
Copy link
Author

I tried master branch but it doesn't support kirkstone. Only scarthgap and nanbield

@davidcodesido
Copy link
Author

I added kirkstone to the layer.conf file but the compilation of rust fails, my bet is that it can't build rust, only rust-native

diff --git a/meta-chromium/conf/layer.conf b/meta-chromium/conf/layer.conf
index ce6372d..98eaa66 100644
--- a/meta-chromium/conf/layer.conf
+++ b/meta-chromium/conf/layer.conf
@@ -9,6 +9,6 @@ BBFILE_PATTERN_chromium-browser-layer := "^${LAYERDIR}/"
 BBFILE_PRIORITY_chromium-browser-layer = "7"

 LAYERVERSION_chromium-browser-layer = "1"
-LAYERSERIES_COMPAT_chromium-browser-layer = "nanbield scarthgap"
+LAYERSERIES_COMPAT_chromium-browser-layer = "nanbield scarthgap kirkstone"

 LAYERDEPENDS_chromium-browser-layer = "clang-layer core openembedded-layer"

@kraj
Copy link
Collaborator

kraj commented May 3, 2024

there is kirkstone branch now so you should try that first for meta-chromium, also go through README in meta-chromium for dependency needs.

@davidcodesido
Copy link
Author

That's my point. I change to kirkstone branch in meta-chromium and it depends of lts-rust-mixins. This is what creates the conflict with meta-rust.

@davidcodesido
Copy link
Author

I see you also maintain lts-rust-mixins @kraj Is there a way for this two projects meta-rust and meta-lts-mixins to coexist? The moment I add the layer for meta-lts-mixins the builds of iotedge fail and with meta-rust only the build for chromium fail. Any help will be welcome since I've spent already weeks trying to figure this one out.

@petergerten
Copy link

same problem here - any workaround?

@Asadeds
Copy link

Asadeds commented Nov 4, 2024

same problem here - any update for this one ?

@MaxIhlenfeldt
Copy link
Collaborator

The moment I add the layer for meta-lts-mixins the builds of iotedge fail

What exactly is the error here?

@Asadeds
Copy link

Asadeds commented Nov 5, 2024

Hi @MaxIhlenfeldt , thanks for your quick reply ,
Actually i am using the distro package of OpenSTlinux , and i used Kirkstone layers, i wanted to install chromium browser on my yocto, i tried to add the meta-browser layers with meta-chromium layers for wayland support, i successfully add and i added the dependencies like , meta-clang, and lts-rust also,
but whenever i try to build it fails on chromum-ozone-wayland : i went through t this page but also failed. "#528 "
what-ever you need to check i will give you the required logs.

ERROR at //build/config/linux/dri/BUILD.gn:11:20: Script returned non-zero exit code.
dri_driver_dir = exec_script(pkg_config_script,
^----------
Current dir: /wrkdirs/usr/ports/www/chromium/work/chromium-125.0.6422.76/out/Release/
Command: python3 /wrkdirs/usr/ports/www/chromium/work/chromium-125.0.6422.76/build/config/linux/pkg-config.py --dridriverdir dri
Returned 1 and printed out:

Error from pkg-config.

See //content/gpu/BUILD.gn:132:18: which caused the file to be included.
configs += [ "//build/config/linux/dri" ]

@MaxIhlenfeldt
Copy link
Collaborator

Thanks for the info! That error is specific to #528, so let's keep the discussion there. Unfortunately I can't really help with that issue.

@MaxIhlenfeldt
Copy link
Collaborator

Note that as described in #852 (comment) this will soon be an issue for Scarthgap as well.

It would still be useful if someone could paste the error message of the cross dependency with meta-rust and meta-lts-mixins.

@EdoardoMolinatti
Copy link

EdoardoMolinatti commented Dec 3, 2024

Hi all, same problem here.
I paste hereafter the error that will popup using Yocto kirkstone, when adding the "meta-browser" layer:

ERROR: Layer 'chromium-browser-layer' depends on layer 'lts-rust-mixin', but this layer is not enabled in your configuration

@MaxIhlenfeldt
Copy link
Collaborator

ERROR: Layer 'chromium-browser-layer' depends on layer 'lts-rust-mixin', but this layer is not enabled in your configuration

Do you have meta-lts-mixins checked out and added to your BBLAYERS?

@EdoardoMolinatti
Copy link

EdoardoMolinatti commented Dec 4, 2024

Do you have meta-lts-mixins checked out and added to your BBLAYERS?

No, but my point is that it wasn't necessary in a previous version.
Could you let me know if you're aware of this new dependency for "kirkstone"?

In any case, I'll checkout the layer repository "meta-lts-mixins" and add it to the BBLAYERS.
I think the repository URL is https://git.yoctoproject.org/git/meta-lts-mixins, right?
(I got that link from the Yocto meta-lts-mixins page)

@MaxIhlenfeldt
Copy link
Collaborator

Could you let me know if you're aware of this new dependency for "kirkstone"?

Yes, we first enabled Rust in #782, and made the dependency explicit in #800 following the discussion in #789.

I think the repository URL is https://git.yoctoproject.org/git/meta-lts-mixins, right?

Yes, that's the correct URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants