From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Kevin Strasser <kevin.strasser@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH] meta-baryon: add build documentation
Date: Wed, 11 Jul 2012 12:10:16 +0100 [thread overview]
Message-ID: <1673385.fOrKr77KPT@helios> (raw)
In-Reply-To: <1341950817-8026-1-git-send-email-kevin.strasser@linux.intel.com>
On Tuesday 10 July 2012 13:06:57 Kevin Strasser wrote:
> Signed-off-by: Kevin Strasser <kevin.strasser@linux.intel.com>
> ---
> README | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/README b/README
> index 2a9c77d..bdd2269 100644
> --- a/README
> +++ b/README
> @@ -27,6 +27,24 @@ to yocto@yoctoproject.org with '[meta-baryon]' in the
> subject.
>
>
>
> +Building the meta-baryon layer
> +------------------------------
> +
> +After you download meta-baryon, be sure add its location to bblayers.conf.
> +
> +The meta-baryon layer uses the 'lame' package, which has a license that
> +must be whitelisted by adding the string "commercial" to the
> +LICENSE_FLAGS_WHITELIST variable in your local.conf. For example:
> +
> + LICENSE_FLAGS_WHITELIST = "commercial"
> +
> +You should then be able to build the image as such:
> +
> + $ source oe-init-build-env
> + $ bitbake baryon-image
> +
> +
> +
> License
> -------
Great stuff. Only thing missing is setting DISTRO = "baryon" in your local.conf
- this is optional, but setting it will cut down DISTRO_FEATURES to something
a bit more appropriate for a headless NAS type device as well as identify the
resulting image as Baryon.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-07-11 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 20:06 [PATCH] meta-baryon: add build documentation Kevin Strasser
2012-07-11 11:10 ` Paul Eggleton [this message]
2012-07-11 17:44 Kevin Strasser
2012-07-11 17:46 ` Robert P. J. Day
2012-07-11 18:05 [PATCH] [meta-baryon] " Kevin Strasser
2012-07-11 20:46 ` Flanagan, Elizabeth
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=1673385.fOrKr77KPT@helios \
--to=paul.eggleton@linux.intel.com \
--cc=kevin.strasser@linux.intel.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.