All of lore.kernel.org
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: "Paul D. DeRocco" <pderocco@ix.netcom.com>
Cc: yocto@yoctoproject.org
Subject: Re: Samba server?
Date: Thu, 28 Mar 2013 11:24:23 +0800	[thread overview]
Message-ID: <5153B7E7.2010403@windriver.com> (raw)
In-Reply-To: <BAEA0795F10B4BF6BD9BAA17CBC46EB0@PAULD>

On 03/28/2013 11:10 AM, Paul D. DeRocco wrote:
>> From: ChenQi
>>
>> http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html
>> section 5.2 Customizing Images
>>
>> In your case, you could add the following line to local.conf.
>> IMAGE_INSTALL_append += "samba"
>>
>> And you can use 'bitbake -g <image_recipe_name>' to see
>> whether samba is pulled in.
>>
>> For all docs, see https://www.yoctoproject.org/documentation/current.
> Thanks for that pointer. I'll try that out.
>
> So is there a general way to peruse the collection of recipes? Does one have
> to do "ls -R *.bb" to get the list of recipes, then read the comments inside
> the files to see how to use them?
>
> And how does one know in advance which ones get included by default? Is
> there some construct one looks for in the .bb file that indicates it gets
> included? Or is there some master recipe that says "this depends upon this
> big long list of standard recipes"?
>
> And are any of the recipes that are included by default not actually
> required, and if so, how do you un-include them if you want to pare down the
> system to a bare minimum?
>
> Or is there some master documentation that I just haven't found that lists
> all the recipes in the Yocto project and gives some guidance on their use?
>
http://docs.openembedded.org/bitbake/html/
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html
The above two manuals might be sufficient for understanding the recipes 
and performing common tasks.

//Chen Qi


  reply	other threads:[~2013-03-28  3:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 23:31 Samba server? Paul D. DeRocco
2013-03-07 10:40 ` Martin Jansa
2013-03-07 18:22   ` Paul D. DeRocco
2013-03-07 18:29     ` Martin Jansa
2013-03-07 22:29       ` Paul D. DeRocco
2013-03-07 22:42         ` Martin Jansa
2013-03-27  8:09           ` Paul D. DeRocco
2013-03-27  9:03             ` Anders Darander
2013-03-27 22:12               ` Paul D. DeRocco
2013-03-28  2:10                 ` ChenQi
2013-03-28  3:10                   ` Paul D. DeRocco
2013-03-28  3:24                     ` ChenQi [this message]
2013-03-28  5:55                     ` Anders Darander
2013-03-28  6:05                       ` Paul D. DeRocco
2013-04-01  9:32                     ` Paul Eggleton
2013-04-01 23:42                       ` Paul D. DeRocco
2013-04-02  7:13                         ` Paul Eggleton
2013-03-28 20:33                   ` Trevor Woerner
2013-03-28 21:35                     ` Paul D. DeRocco
2013-03-28 21:44                       ` Trevor Woerner

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=5153B7E7.2010403@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=pderocco@ix.netcom.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.