All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trillo <martri@arantia.com>
To: zboszor@pr.hu
Cc: meta-freescale@yoctoproject.org
Subject: Re: Chromium acceleration
Date: Tue, 25 Mar 2014 10:46:47 +0100	[thread overview]
Message-ID: <53315087.9040101@arantia.com> (raw)
In-Reply-To: <16ba811c114eea4c4dfc575f7e117ffd.squirrel@webmail.prtelecom.hu>

Hi,

On 03/25/2014 10:32 AM, zboszor@pr.hu wrote:
> Hi,
>
> how can I add the meta-browser tree to the set of recipes? I did:
>
> $ cd fsl-community-bsp/sources
> $ git clone https://github.com/OSSystems/meta-browser.git
> $ cd ..
> $ . ./setup-environment build-master-next/
> $ bitbake chromium
> Loading cache: 100%
> |###########################################################################################################################|
> ETA:  00:00:00
> Loaded 1806 entries from dependency cache.
> ERROR: Nothing PROVIDES 'chromium'
>
> Summary: There was 1 WARNING message shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
> [zozo@localhost build-master-next]$
>
> Where should I move the meta-browser directory from the toplevel "sources"?
> What else should be done?

You need to add the "meta-browser" layer to your bblayers.conf (in 
build/conf/), like this:

BBLAYERS += " ${BSPDIR}/sources/meta-browser "

You will probably need other to add other layers such as "meta-gnome".

Hope it helps,
Marco.





  parent reply	other threads:[~2014-03-25  9:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  9:32 Chromium acceleration zboszor
2014-03-25  9:35 ` Eric Bénard
2014-03-25  9:46 ` Marco Trillo [this message]
2014-03-25 12:58   ` Boszormenyi Zoltan
  -- strict thread matches above, loose matches on Subject: below --
2014-11-27 10:14 Becue Paul
2014-12-01 14:34 ` Daiane Angolini
2014-12-01 15:07   ` Otavio Salvador
2014-03-19 20:49 Eric Nelson
2014-03-19 21:00 ` Carlos Rafael Giani
2014-03-19 22:40   ` Eric Nelson
2014-03-20  1:29     ` Christian Betz
2014-03-20  2:50       ` Eric Nelson
2014-03-20  8:30         ` Carlos Rafael Giani
2014-03-20 12:22           ` Otavio Salvador
2014-03-20 14:07             ` Christian Betz
2014-03-20 15:02               ` Otavio Salvador
2014-03-20 14:29             ` Eric Nelson
2014-03-20 14:58               ` Otavio Salvador
2014-03-21 11:49                 ` Diego
2014-03-21 14:17                   ` Eric Nelson
2014-03-20 13:46           ` Christian Betz
2014-03-20 23:19             ` Carlos Rafael Giani
2014-03-21 12:21               ` Dmitriy B.
2014-04-01 19:22               ` Eric Nelson
2014-04-02 10:21                 ` Carlos Rafael Giani
2014-04-02 10:28                   ` Gary Thomas
2014-04-02 10:33                     ` Carlos Rafael Giani
     [not found]                 ` <533BE4A3.7040301@pr.hu>
2014-04-02 10:23                   ` Carlos Rafael Giani
2014-04-02 11:12                     ` Boszormenyi Zoltan
2014-04-02 12:02                     ` Christian Betz
2014-04-02 12:28                       ` Carlos Rafael Giani
2014-04-04  9:28                         ` Boszormenyi Zoltan
2014-04-02 10:29                 ` Boszormenyi Zoltan
2014-04-02 14:16                   ` Eric Nelson
2014-03-20 12:47 ` Lauren Post
2014-03-20 14:25   ` Eric Nelson
2014-03-20 14:27     ` Lauren Post

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=53315087.9040101@arantia.com \
    --to=martri@arantia.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=zboszor@pr.hu \
    /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.