From: Christian Eggers <ceggers@arri.de>
To: <docs@lists.yoctoproject.org>
Cc: Mark Hatle <mark.hatle@kernel.crashing.org>
Subject: Re: [docs] Best practices documentation for multiconfigs
Date: Thu, 9 Jan 2025 09:14:15 +0100 [thread overview]
Message-ID: <4928529.OV4Wx5bFTl@n9w6sw14> (raw)
In-Reply-To: <39d815da-1f48-4822-a1c2-1d8762ab7989@kernel.crashing.org>
Hi,
due to this thread I got noticed about the "multiconfig" feature for
the first time. I have two additional questions related to this topic:
1. Toolchain
For baremetal targets we currently use the "GNUARM" toolchain. Would it
make sense to build the "secondary" toolchain with Yocto instead? Other
users may prefer staying at an external toolchain. Is there already
documentation about building a secondary toolchain (or using an existing one)?
2. SDK
How can the additional components of a multiconfig (e.g. toolchain, libraries)
be added to the SDK?
regards,
Christian
next prev parent reply other threads:[~2025-01-09 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 23:07 Best practices documentation for multiconfigs Mark Hatle
2025-01-07 23:37 ` [docs] " Joshua Watt
2025-01-08 15:34 ` Mark Hatle
2025-01-09 8:14 ` Christian Eggers [this message]
2025-01-09 15:35 ` Mark Hatle
2025-01-08 15:31 ` Antonin Godard
2025-01-08 15:38 ` Mark Hatle
2025-01-14 9:52 ` [docs] " Quentin Schulz
2025-01-16 3:32 ` Mark Hatle
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=4928529.OV4Wx5bFTl@n9w6sw14 \
--to=ceggers@arri.de \
--cc=docs@lists.yoctoproject.org \
--cc=mark.hatle@kernel.crashing.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