From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jim Abernathy <jfabernathy@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: meta-baryon
Date: Wed, 11 Jul 2012 18:42:09 +0100 [thread overview]
Message-ID: <35320765.Si4aS1H0Ml@helios> (raw)
In-Reply-To: <4FFDB177.4000208@gmail.com>
On Wednesday 11 July 2012 13:01:43 Jim Abernathy wrote:
> On 07/11/2012 12:49 PM, Jim Abernathy wrote:
> > When you do have time, let me know if my assumptions above were
> > correct. I must be missing something because I can't find any
> > evidence of webmin in the file system. So while my board boots Yocto,
> > I can't see any of the baryon layer. Could a CORE-IMAGE-EXTRA-INSTALL
> > or something be needed to force the inclusion into the file system??
>
> Never mind. Because baryon is on master and poky is on edison, there
> are some issues like:
>
> 1. the baryon-image.bb uses CORE_IMAGE_EXTRA_INSTALL instead of what
> edison needed,which was POKY_EXTRA_INSTALL
Ah, well spotted - actually it should not really be using that variable. I
have a fix which I'll send out to use IMAGE_INSTALL instead.
> 2. ffmpeg needs COMMERCIAL_LICENSE = yes instead of
> LICENSE_FLAGS_WHITELIST += "commercial"
It seems we really need an edison branch where the documentation can say the
right thing for each branch (and we can avoid introducing any future
incompatibilities). Once the above fix is merged I'll create an edison branch
so we can do this.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2012-07-11 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 19:47 meta-baryon Jim Abernathy
2012-07-11 15:39 ` meta-baryon Jim Abernathy
2012-07-11 15:47 ` meta-baryon Paul Eggleton
2012-07-11 16:49 ` meta-baryon Jim Abernathy
2012-07-11 17:01 ` meta-baryon Jim Abernathy
2012-07-11 17:42 ` Paul Eggleton [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=35320765.Si4aS1H0Ml@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jfabernathy@gmail.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.