From: "Khem Raj" <raj.khem@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] first of many questions on wic and associated documentation
Date: Sun, 15 Aug 2021 11:33:42 -0700 [thread overview]
Message-ID: <CAMKF1srSBN4kOK8=huWg4Vnxz3GG2PMnx6Afc34LEtbUw5g4Yw@mail.gmail.com> (raw)
In-Reply-To: <b94dc1e7-9ba-58c6-9236-9c89cf23f83@crashcourse.ca>
On Sun, Aug 15, 2021 at 11:16 AM Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
>
> as i am just beginning my adventure with the current wic
> documentation, i suspect i will have many questions, so let's start
> here:
>
> http://docs.yoctoproject.org/dev-manual/common-tasks.html#requirements
>
> first, the docs imply that you have to manually build some packages:
>
> "You must build several native tools, which are built to run on the
> build system:
>
> $ bitbake parted-native dosfstools-native mtools-native"
>
I think this perhaps can be omitted.
> except that there is a "wic-tools.bb" recipe that appears to handle
> that, and i'm going to assume it's called as part of the wic
> processing, so that the doc seems a bit over-ambitious in what it
> needs the developer to do.
>
> and right below that:
>
> "Include the name of the wic kickstart file as part of the WKS_FILE
> variable"
>
> except that makes no mention of the WKS_FILES variable.
>
> thoughts?
maybe WKS_FILES should be better documented as well.
>
> rday
>
>
>
next prev parent reply other threads:[~2021-08-15 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 18:16 first of many questions on wic and associated documentation Robert P. J. Day
2021-08-15 18:33 ` Khem Raj [this message]
2021-08-16 8:09 ` [docs] " Robert P. J. Day
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='CAMKF1srSBN4kOK8=huWg4Vnxz3GG2PMnx6Afc34LEtbUw5g4Yw@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.