All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: yocto@yoctoproject.org
Subject: Re: bitbake user manual vs mega manual, and more info on local file fetcher?
Date: Mon, 17 Dec 2012 20:26:58 -0500	[thread overview]
Message-ID: <50CFC662.7050608@mindchasers.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946ACCE36@ORSMSX101.amr.corp.intel.com>

Hi,

I'm glad to hear that the bitbake manual is getting an update, and I'm 
sure you guys know a lot of debugging tricks that I don't know.

Can you please include a section on debugging bitbake build errors 
(beyond logs, -D, and -v)?  In other words, what's the best way to 
instrument or hack bitbake when debugging errors in the build process?

I sometimes hack at the python to better understand what's going on, so 
I'm interested to see what the experts do.

Thanks,

Bob





On 12/13/2012 10:18 AM, Rifenbark, Scott M wrote:
> Hey Robert,
>
> Great questions... we are revising the BitBake manual as part of the YP 1.4 release.  And, we are currently discussing exactly how to position it.  So the answers to your questions are in the works.
>
> Scott
>
>> -----Original Message-----
>> From: yocto-bounces@yoctoproject.org [mailto:yocto-
>> bounces@yoctoproject.org] On Behalf Of Robert P. J. Day
>> Sent: Thursday, December 13, 2012 6:09 AM
>> To: Yocto discussion list
>> Subject: [yocto] bitbake user manual vs mega manual, and more info on
>> local file fetcher?
>>
>>
>>   first question -- is the bitbake user manual that comes bundled with
>> the bitbake source considered part of the yocto doc collection?  as
>> in, if one wants detailed info on bitbake, does one read the bitbake
>> user manual (which is not mentioned on the yocto docs page), or is
>> bitbake user info assumed to now be scattered throughout the yocto
>> docs?  i think it's important to identify the canonical location for
>> that documentation.
>>
>>   following on that, i'm asking since the bitbake user manual is
>> definitely a *little* deficient on info for the local file fetcher.
>> here's the sum total of its examples:
>>
>> SRC_URI= "file://relativefile.patch"
>> SRC_URI= "file://relativefile.patch;this=ignored"
>> SRC_URI= "file:///Users/ich/very_important_software"
>>
>> but there's no mention that (as i read it) that protocol accepts
>> wildcards:
>>
>> meta-angstrom/recipes-angstrom/angstrom/angstrom-uboot-
>> scripts.bb:SRC_URI = "file://*.cmd"
>>
>> i had no idea that was even true until i stumbled over the above (if
>> that's indeed what it means).
>>
>>   there's also no comprehensive coverage of how to define and use
>> patches in the yocto docs.  the only mention i see is in the ref
>> manual, in the variable glossary under SRC_URI, which isn't even
>> complete (no mention of apply= or patchdir=).
>>
>>   so basic question -- is the bitbake user manual still under active
>> maintenance and is it considered part of the yocto docs collection?
>> since all that bitbake information should be *somewhere* but it's not
>> clear where.
>>
>> rday
>>
>>
>> --
>>
>> ========================================================================
>> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>>                         http://crashcourse.ca
>>
>> Twitter:                                       http://twitter.com/rpjday
>> LinkedIn:                               http://ca.linkedin.com/in/rpjday
>> ========================================================================
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



      parent reply	other threads:[~2012-12-18  1:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 14:08 bitbake user manual vs mega manual, and more info on local file fetcher? Robert P. J. Day
2012-12-13 15:18 ` Rifenbark, Scott M
2012-12-15 15:53   ` Trevor Woerner
2012-12-15 19:56     ` Bill Traynor
2012-12-18  1:26   ` Bob Cochran [this message]

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=50CFC662.7050608@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=yocto@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 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.