public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: Antonin Godard <antonin.godard@bootlin.com>, docs@lists.yoctoproject.org
Cc: michael.opdenacker@rootcommit.com
Subject: Re: [docs] [PATCH 2/3] dev-manual/bmaptool.rst: add missing command for bmaptool-native
Date: Wed, 04 Dec 2024 10:31:07 +0000 (UTC)	[thread overview]
Message-ID: <b10002a9-e9dd-4ab1-9cdb-312db5df9509@rootcommit.com> (raw)
In-Reply-To: <D613DDACPBYI.1YDZEEN2GB07L@bootlin.com>

Hi Antonin

On 12/2/24 10:02, Antonin Godard wrote:
> Hi Michael,
>
> On Sun Dec 1, 2024 at 6:38 PM CET, Michael Opdenacker via lists.yoctoproject.org wrote:
>> From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>>
>> Otherwise, running "oe-run-native bmaptool-native bmaptool ..."
>> fails as follows:
>>
>> Error: Have you run 'bitbake bmaptool-native -caddto_recipe_sysroot'?
>>
>> Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
>> ---
>>   documentation/dev-manual/bmaptool.rst | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/documentation/dev-manual/bmaptool.rst b/documentation/dev-manual/bmaptool.rst
>> index 493abf7607..5fc46c7792 100644
>> --- a/documentation/dev-manual/bmaptool.rst
>> +++ b/documentation/dev-manual/bmaptool.rst
>> @@ -23,6 +23,7 @@ system image files much faster.
>>         need to build `bmaptool` before using it. Use the following command::
> s/command/commands/ or see comment below
>
>>   
>>            $ bitbake bmaptool-native
>> +         $ bitbake bmaptool-native -caddto_recipe_sysroot
> Isn't running `bitbake bmaptool-native -caddto_recipe_sysroot` enough? I
> would say addto_recipe_sysroot implies building the recipe, but I might be
> wrong!

Good catch. Indeed the second command is enough.
I'm preparing an update.

Thanks!
Michael.

-- 
Michael Opdenacker
Root Commit
Embedded Linux Training and Consulting
https://rootcommit.com/



  reply	other threads:[~2024-12-04 10:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-01 17:38 [PATCH 1/3] dev-manual: fix styling of references to bmaptool michael.opdenacker
2024-12-01 17:38 ` [PATCH 2/3] dev-manual/bmaptool.rst: add missing command for bmaptool-native michael.opdenacker
2024-12-02  9:02   ` [docs] " Antonin Godard
2024-12-04 10:31     ` Michael Opdenacker [this message]
2024-12-01 17:38 ` [PATCH 3/3] dev-manual/bmaptool.rst: simplify and fix instructions michael.opdenacker
2024-12-01 19:26   ` [docs] " Ulrich Ölmann
2024-12-04  9:19     ` Michael Opdenacker
2024-12-02  9:02   ` Antonin Godard
2024-12-04  9:26     ` Michael Opdenacker
2024-12-04  9:33       ` Michael Opdenacker
2024-12-04 10:17         ` Antonin Godard

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=b10002a9-e9dd-4ab1-9cdb-312db5df9509@rootcommit.com \
    --to=michael.opdenacker@rootcommit.com \
    --cc=antonin.godard@bootlin.com \
    --cc=docs@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