Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser][PATCH 0/1] chromium: add support for x86-64
Date: Fri, 8 Mar 2013 17:02:47 +0100	[thread overview]
Message-ID: <20130308170247.30dfa092@e6520eb> (raw)
In-Reply-To: <1362746826-22762-1-git-send-email-laurentiu.palcu@intel.com>

Hi Laurentiu,

Le Fri,  8 Mar 2013 14:47:05 +0200,
Laurentiu Palcu <laurentiu.palcu@intel.com> a écrit :
> I gave chromium a test on x86 architecture and, apparently, there was no
> support for x86-64. So, I added it (didn't do much actually, just copied
> the i586 gypi files and changed the target_arch to x64), built
> core-image-sato for qemux86-64, and ran chrome. It worked just fine.
> 
> I also removed gtk+-native from the dependencies (there's no need for
> the native gtk) and added gtk+ instead (this one is needed).
> 
thanks I splitted the change in 2 patches and pushed it.

Eric



      parent reply	other threads:[~2013-03-08 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 12:47 [meta-browser][PATCH 0/1] chromium: add support for x86-64 Laurentiu Palcu
2013-03-08 12:47 ` [meta-browser][PATCH 1/1] " Laurentiu Palcu
2013-03-08 16:02 ` Eric Bénard [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=20130308170247.30dfa092@e6520eb \
    --to=eric@eukrea.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox