All of lore.kernel.org
 help / color / mirror / Atom feed
* bitbake user manual vs mega manual, and more info on local file fetcher?
@ 2012-12-13 14:08 Robert P. J. Day
  2012-12-13 15:18 ` Rifenbark, Scott M
  0 siblings, 1 reply; 5+ messages in thread
From: Robert P. J. Day @ 2012-12-13 14:08 UTC (permalink / raw)
  To: Yocto discussion list


  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
========================================================================


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: bitbake user manual vs mega manual, and more info on local file fetcher?
  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-18  1:26   ` Bob Cochran
  0 siblings, 2 replies; 5+ messages in thread
From: Rifenbark, Scott M @ 2012-12-13 15:18 UTC (permalink / raw)
  To: Robert P. J. Day, Yocto discussion list

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: bitbake user manual vs mega manual, and more info on local file fetcher?
  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
  1 sibling, 1 reply; 5+ messages in thread
From: Trevor Woerner @ 2012-12-15 15:53 UTC (permalink / raw)
  To: Rifenbark, Scott M; +Cc: Yocto discussion list

On Thu, Dec 13, 2012 at 10:18 AM, Rifenbark, Scott M
<scott.m.rifenbark@intel.com> wrote:
> we are revising the BitBake manual as part of the YP 1.4 release


Personally I think it would be great if the bitbake documentation
could be updated to include some of the information from Eren's
document as well. Eren provides a "hands-on" demonstration of how
bitbake works (and how to work with bitbake). The current
documentation reads more like a dictionary (which is great if someone
is looking for a dictionary-like treatment of bitbake).


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: bitbake user manual vs mega manual, and more info on local file fetcher?
  2012-12-15 15:53   ` Trevor Woerner
@ 2012-12-15 19:56     ` Bill Traynor
  0 siblings, 0 replies; 5+ messages in thread
From: Bill Traynor @ 2012-12-15 19:56 UTC (permalink / raw)
  To: Trevor Woerner; +Cc: Yocto discussion list

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

On Sat, Dec 15, 2012 at 10:53 AM, Trevor Woerner <twoerner@gmail.com> wrote:

> On Thu, Dec 13, 2012 at 10:18 AM, Rifenbark, Scott M
> <scott.m.rifenbark@intel.com> wrote:
> > we are revising the BitBake manual as part of the YP 1.4 release
>
>
> Personally I think it would be great if the bitbake documentation
> could be updated to include some of the information from Eren's
> document as well. Eren provides a "hands-on" demonstration of how
> bitbake works (and how to work with bitbake). The current
> documentation reads more like a dictionary (which is great if someone
> is looking for a dictionary-like treatment of bitbake).
>

I assume you're referring to Eren's blog post:
http://hambedded.org/blog/categories/bitbake/

I'll be doing the bitbake manual update and will integrate similar
information into the manual, or perhaps as new document in addition to the
Bitbake manual.


> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 2005 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: bitbake user manual vs mega manual, and more info on local file fetcher?
  2012-12-13 15:18 ` Rifenbark, Scott M
  2012-12-15 15:53   ` Trevor Woerner
@ 2012-12-18  1:26   ` Bob Cochran
  1 sibling, 0 replies; 5+ messages in thread
From: Bob Cochran @ 2012-12-18  1:26 UTC (permalink / raw)
  To: yocto

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
>



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2012-12-18  1:27 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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.