All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] is there an actual "Getting Started" guide?
Date: Wed, 11 May 2022 12:49:48 +0200	[thread overview]
Message-ID: <36a536ea-b77e-6e9e-e9c4-00a3790fb32d@theobroma-systems.com> (raw)
In-Reply-To: <e14d577f-fe71-d71e-6eaf-2e87214a593f@crashcourse.ca>



On 5/11/22 12:41, Robert P. J. Day wrote:
> On Wed, 11 May 2022, Quentin Schulz wrote:
> 
>> Hi Robert,
>>
>> On 5/11/22 12:28, Robert P. J. Day wrote:
>>>
>>>     was building a fresh ubuntu 22.04 build machine for OE/YP, starting
>>> with minimal install to see how much more i would have to add, and
>>> got (via sanity.bbclass) a missing module message based on:
>>>
>>> status.addresult('Your Python 3 is not a full install. Please install
>>> the module %s (see the Getting Started guide for further
>>> information).\n' % e.name)
>>>
>>>     note the reference to the "Getting Started guide", which does not
>>> seem to exist (anymore?). where *would* one go to resolve an error of
>>> the form "missing distutils.sysconfig" absent a Getting Started guide?
>>>
>>
>> I think this is what you're after?
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.yoctoproject.org_ref-2Dmanual_system-2Drequirements.html&d=DwIBAg&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=yPuNzagIy_whkBE_pem1x9YQx7w5lvQlVIoLNlaMimJyeWKCJdIPq9TjDyYGWrjs&s=24h3qNQNp2mMdaiqx5o7n3youEbYKRITx0hwOnd9Mdo&e=
>>
>> If so, please send a patch to update the error code to point to this
>> piece of documentation :)
> 
>    i *suspected* it was something like that, just wanted to make sure
> there was no "getting started" guide i'd managed to miss all this
> time.  will send patch to OE list.
> 

I think it *might* actually be 
https://docs.yoctoproject.org/dev-manual/start.html.

c.f.
https://git.yoctoproject.org/yocto-docs/commit/?id=028f8f7a1b93a023a99ffadb01b0da699b4081c2

Either way, it needs to be fixed :)

Cheers,
Quentin


  reply	other threads:[~2022-05-11 10:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 10:28 is there an actual "Getting Started" guide? Robert P. J. Day
2022-05-11 10:37 ` [docs] " Quentin Schulz
2022-05-11 10:41   ` Robert P. J. Day
2022-05-11 10:49     ` Quentin Schulz [this message]
2022-05-11 11:11       ` Robert P. J. Day
2022-05-11 15:27         ` Khem Raj

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=36a536ea-b77e-6e9e-e9c4-00a3790fb32d@theobroma-systems.com \
    --to=quentin.schulz@theobroma-systems.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.