[yocto] Yocto Labs (Alex J Lennon)
Kashyap Gada
gada.kashyap at gmail.com
Sun Jun 22 22:41:32 PDT 2014
I personally donot think the manuals are abstract, instead they are very
detailed. You have got a quick start guide which can help you alot for
starting up. You can read some important points at
http://www.kashyapgada.com/2014/06/12/embedded-linux-building-an-image-using-yocto-project/
. There are also more advanced manuls, project development, application
development manuals. Above all next month there will be a book releasing
named Embedded Linux Development with Yocto Project
http://www.packtpub.com/embedded-linux-development-with-yocto-project/book
which might also be a good guide, I am looking forward to that book, Have
already pre booked it.
Kashyap Gada
On Mon, Jun 23, 2014 at 12:30 AM, <yocto-request at yoctoproject.org> wrote:
> Send yocto mailing list submissions to
> yocto at yoctoproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-request at yoctoproject.org
>
> You can reach the person managing the list at
> yocto-owner at yoctoproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
>
>
> Today's Topics:
>
> 1. Yocto Labs (Arun Kumar)
> 2. Re: Yocto Labs (Alex J Lennon)
> 3. the apparent need for docbook <replaceable> tag in manual
> examples (Robert P. J. Day)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 22 Jun 2014 06:03:58 +0530
> From: Arun Kumar <arunkr.linux at gmail.com>
> To: Yocto Mailing List <yocto at yoctoproject.org>
> Subject: [yocto] Yocto Labs
> Message-ID: <53A62476.2080008 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi,
>
> I am new to Yocto project and have been following the documentation
> for familiarity.
> I am looking for hands on lab sessions for the yocto project.
> I am unable to find the same on INTERNET, all i find is conference
> videos and presentation.
>
> If anyone can share links to online tutorial videos / pdfs it would be
> really useful.
> content like creating and deploying own recipe files, layers. The
> Documentation describes these tasks at a very abstract level, an little
> more advanced version of the same would be appreciated.
> Thanks in advance...
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 22 Jun 2014 09:54:25 +0100
> From: Alex J Lennon <ajlennon at dynamicdevices.co.uk>
> To: Arun Kumar <arunkr.linux at gmail.com>, Yocto Mailing List
> <yocto at yoctoproject.org>
> Subject: Re: [yocto] Yocto Labs
> Message-ID: <53A699C1.4040405 at dynamicdevices.co.uk>
> Content-Type: text/plain; charset=ISO-8859-1
>
>
> On 22/06/2014 01:33, Arun Kumar wrote:
> > Hi,
> >
> > I am new to Yocto project and have been following the
> > documentation for familiarity.
> > I am looking for hands on lab sessions for the yocto project.
> > I am unable to find the same on INTERNET, all i find is conference
> > videos and presentation.
> >
> > If anyone can share links to online tutorial videos / pdfs it would be
> > really useful.
> > content like creating and deploying own recipe files, layers. The
> > Documentation describes these tasks at a very abstract level, an
> > little more advanced version of the same would be appreciated.
> > Thanks in advance...
>
> Might be of some use Arun,
>
>
> https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles
>
> Regards,
>
> Alex
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 22 Jun 2014 09:20:15 -0400 (EDT)
> From: "Robert P. J. Day" <rpjday at crashcourse.ca>
> To: Yocto discussion list <yocto at yoctoproject.org>
> Subject: [yocto] the apparent need for docbook <replaceable> tag in
> manual examples
> Message-ID: <alpine.LFD.2.11.1406220901500.2299 at localhost>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> something poor scott rifenbark can ponder in his copious free time
> :-), but i think some of the current examples in the various manuals
> need to be enhanced with the use of the docbook <replaceable> tag to
> emphasize that they are generic references meant to be replaced by
> specific values; otherwise, there's potential confusion.
>
> as a concrete example, i remember *way* back when i was reading
> about conditional metadata in the bitbake user manual, particularly
> this verbatim example:
>
> OVERRIDES = "architecture:os:machine"
> TEST = "default"
> TEST_os = "osspecific"
> TEST_nooverride = "othercondvalue"
>
> because all of the above is currently rendered in the same (courier)
> font in the generated manual, i mistakenly thought that all of the
> above was to somehow be typed exactly that way, and i was completely
> baffled as to what the qualifiers "_os" and "_nooverride" would do. it
> was only after searching for examples in the codebase that it dawned
> that those strings were meant to be replaced by actual examples of the
> current architecture, os, machine and so on.
>
> duh.
>
> this can be made more obvious fairly simply with the following
> tweak of using the docbook <replaceable> tag:
>
> diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> index a9f5072..f8be373 100644
> --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
> @@ -359,7 +359,7 @@
> version.
> Here is an example:
> <literallayout class='monospaced'>
> - OVERRIDES = "architecture:os:machine"
> + OVERRIDES =
> "<replaceable>architecture</replaceable>:<replaceable>os</replaceable>:<replaceable>machine</replaceable>"
> TEST = "default"
> TEST_os = "osspecific"
> TEST_nooverride = "othercondvalue"
>
> i've confirmed that that tag is processed properly within a
> <literallayout>, and renders in italicized courier font, which is the
> visual clue that it's not meant to be read literally.
>
> oh, and one more related point ... i think it would be more useful
> to replace generic manual examples that use meaningless phrases such
> as "foo" and "bar" with specific examples yanked from the actual OE
> codebase.
>
> as i said, it took me a few minutes to figure out what the
> conditional metadata example above was trying to demonstrate, but as
> soon as i saw a real example in the codebase, it was perfectly clear.
> to this end, i'm creating wiki pages that show stuff like that
> exactly, like this one for conditional overrides:
>
> http://www.crashcourse.ca/wiki/index.php/BitBake_Overrides
>
> so rather than try to explain the generic concept, i can just bring up
> the wiki page and say, "see? that's how it works." and everyone
> understands immediately.
>
> anyway, just my $0.02. back to work ...
>
> 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 at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
> End of yocto Digest, Vol 45, Issue 90
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20140623/84625bfe/attachment.html>
More information about the yocto
mailing list