From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Randy MacLeod <randy.macleod@windriver.com>, JC <jc@vtkloud.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: lib ao ?
Date: Mon, 16 Sep 2013 16:37:50 +0100 [thread overview]
Message-ID: <3047549.YMT2qeacCQ@helios> (raw)
In-Reply-To: <52371CDF.4020607@windriver.com>
On Monday 16 September 2013 10:59:43 Randy MacLeod wrote:
> On 13-09-13 07:12 PM, JC wrote:
> > Hi,
> >
> > I cannot find a trace of libao. Is this present somewhere in some
>
> It is:
> http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/libao/libao_
> 0.8.8.bb
> > openembedded-* repo I would have missed ? I could not find it in
> > layers.openembedded.org
There isn't currently a libao recipe in common OE-Core based layers indexed by
the layer index. FYI though there is a recipe in the unofficial (and apparently
unmaintained) meta-jlime layer here:
https://github.com/tworaz/oe-tworaz/tree/master/meta-jlime
It would be great to have this added to meta-multimedia - please test it and
if it works for you please feel free to send a patch adding it to meta-
multimedia.
> The UI for that site has changed, you have to set:
> Branch: OE-Classic
> to search meta-openembedded.
>
> Painful, I know, but I assume there was confusion about what's in
> oe-core and what's in OE-Classic.
This is *not* correct. OE-Classic as shown in the layer index is OE-Classic,
the old monolithic OpenEmbedded; it is not the same thing as meta-oe or any of
the layers in the meta-openembedded repository.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-09-16 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 23:12 lib ao ? JC
2013-09-16 14:59 ` Randy MacLeod
2013-09-16 15:37 ` Paul Eggleton [this message]
2013-09-16 15:39 ` JC
2013-09-17 10:36 ` Jean-Charles JC Verdié
2013-09-17 10:51 ` Paul Eggleton
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=3047549.YMT2qeacCQ@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jc@vtkloud.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox