From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Michel Alex <Alex.Michel@wiedemann-group.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] need help for fixing some build problems
Date: Mon, 3 Jun 2024 15:39:47 +0200 [thread overview]
Message-ID: <Zl3Ho5PE1PVMushc@landeda> (raw)
In-Reply-To: <AS1P250MB0608C9F89F3830573FAD7932A9FF2@AS1P250MB0608.EURP250.PROD.OUTLOOK.COM>
Michel, All,
Thanks for helping fix build failures ! :-)
On 2024-06-03 13:26 +0000, Michel Alex spake thusly:
> I have a question about libzenoh-c package, which currently can not be build by the autobuilder for following architectures:
> http://autobuild.buildroot.net/results/680f25769526e5eef43d254a10a525b165846c75/
> http://autobuild.buildroot.net/results/31ed69cb2ffe8e9bc13a27c3fda16c27e9855b56/
> http://autobuild.buildroot.net/results/fdc74b8a42388b51cc4197c38b552559b97cbb8c/
> http://autobuild.buildroot.net/results/6e7ad53d44b417f6aa62acd8b2396720f5a14e82/
>
> The zenoh-c help page says that "zenoh-c only have support for
> following targets: aarch64-unknown-linux-gnu, x86_64-unknown-linux-gnu,
> arm-unknown-linux-gnueabi".
>
> What is the correct way to add a dependency to Config.in file which
> enables the libzenoh-c only if above targets are selected?
Se the manual for how to do that:
https://buildroot.org/downloads/manual/manual.html#_config_files
Basically, you'd introduce a blind option (elided for brevity):
config BR2_PACKAGE_LIBZENOH_C_ARCH_SUPPORTS
bool
depends on BR2_PACKAGE_HOST_RUSTC_TARGET_ARCH_SUPPORTS
default y if BR2_aarch64
default y if BR2_arm
default y if BR2_x86_64
config BR2_PACKAGE_LIBZENOH_C_ARCH_SUPPORTS
bool "zenoh-c"
depends on BR2_PACKAGE_LIBZENOH_C_ARCH_SUPPORTS
depends on BR2_TOOLCHAIN_USES_GLIBC
comment "zenoh-c needs a glibc toolchain"
depends on BR2_PACKAGE_LIBZENOH_C_ARCH_SUPPORTS
depends on !BR2_TOOLCHAIN_USES_GLIBC
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-06-03 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 13:26 [Buildroot] need help for fixing some build problems Michel Alex
2024-06-03 13:39 ` Yann E. MORIN [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Zl3Ho5PE1PVMushc@landeda \
--to=yann.morin.1998@free.fr \
--cc=Alex.Michel@wiedemann-group.com \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox