poky.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: "nicolas.wirth@speedgoat.ch" <nicolas.wirth@speedgoat.ch>
Cc: "poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>
Subject: Re: [poky] Running chroot-like command in Yocto #yocto
Date: Wed, 15 May 2024 13:52:34 +0000	[thread overview]
Message-ID: <EFDF2248-3DF0-4B41-B58D-B9437E75645D@arm.com> (raw)
In-Reply-To: <19808.1715776447222316220@lists.yoctoproject.org>



> On 15 May 2024, at 13:34, Nicolas Wirth via lists.yoctoproject.org <nicolas.wirth=speedgoat.ch@lists.yoctoproject.org> wrote:
> 
> Really good point, my example can be misleading. I didn't wanted to add confusion by fully explaining my goal.
> 
> The goal is to run extlinux --install ${IMAGE_ROOTFS}/boot/syslinux, as I've understood, this command install the sylinux required file but also does write some bytes at the start of the partition, for the MBR. In debbos, I could do that using the following code and now I'm trying to reproduce that in the Yocto build system:
>   - action: run
>     description: Set up Syslinux
>     chroot: true
>     command: extlinux --install /boot/syslinux

The syslinux class already basically does a lot of this.  If you want to do something bespoke and custom you just ensure do_image depends on syslinux-native and run the commands in an IMAGE_POSTPROCESS_COMMAND.  But if you’re generating the correct image type then this will be done already.

Ross

  parent reply	other threads:[~2024-05-15 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 12:14 Running chroot-like command in Yocto #yocto Nicolas Wirth
2024-05-15 12:19 ` [poky] " Alexander Kanavin
2024-05-15 12:34   ` Nicolas Wirth
2024-05-15 13:08     ` [poky] " Alexander Kanavin
2024-05-15 13:52     ` Ross Burton [this message]
2024-05-15 14:42       ` Nicolas Wirth
2024-05-16  3:36         ` [poky] " Chen, Qi

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=EFDF2248-3DF0-4B41-B58D-B9437E75645D@arm.com \
    --to=ross.burton@arm.com \
    --cc=nicolas.wirth@speedgoat.ch \
    --cc=poky@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).