From: "embedded.yogesh" <embedded.yogesh@gmail.com>
To: poky@yoctoproject.org
Subject: Re: chromium browser
Date: Mon, 21 Feb 2011 11:03:01 +0530 [thread overview]
Message-ID: <4D61F90D.606@gmail.com> (raw)
In-Reply-To: <4D50C055.5080200@gmail.com>
Hi,
I tried to pull Chrome from OpenEmbedded and also pulled in its deps .
But at the time of building chrome getting following errors can any one
have any idea ?
| + oe_runmake -r BUILDTYPE=Release
| + '[' xmake = x ']'
| + oenote make -e MAKEFLAGS= -r BUILDTYPE=Release
| elease'
| NOTE: make -e MAKEFLAGS= -r BUILDTYPE=Release
| + make -e MAKEFLAGS= -r BUILDTYPE=Release
| CXX(target) out/Release/obj.target/app_base/ui/base/animation/animation.o
| cc1plus: warnings being treated as errors
| cc1plus: error: include location "/usr/include/libpng12" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/gtk-2.0" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/atk-1.0" is unsafe for cross-compilation
| cc1plus: error: include location
| + echo NOTE: 'make -e MAKEFLAGS= -r BUILDTYPE=Release'
| NOTE: make -e MAKEFLAGS= -r BUILDTYPE=Release
| + make -e MAKEFLAGS= -r BUILDTYPE=Release
| CXX(target) out/Release/obj.target/app_base/ui/base/animation/animation.o
| cc1plus: warnings being treated as errors
| cc1plus: error: include location "/usr/include/libpng12" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/gtk-2.0" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/atk-1.0" is unsafe for cross-compilation
| "/usr/include/cairo" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/pango-1.0" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/gio-unix-2.0/" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/glib-2.0" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/pixman-1" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/freetype2" is unsafe for cross-compilation
| cc1plus
| cc1plus: error: include location "/usr/include/cairo" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/pango-1.0" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/gio-unix-2.0/" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/glib-2.0" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/pixman-1" is unsafe for cross-compilation
| cc1plus: error: include location "/usr/include/freetype2" is unsafe for cross-compilation
| : error: include location "/usr/include/directfb" is unsafe for cross-compilation
| make: *** [out/Release/obj.target/app_base/ui/base/animation/animation.o] Error 1
| + die 'oe_runmake failed'
| + oefatal 'oe_runmake failed'
| + echo FATAL: 'oe_runmake failed'
| FATAL: oe_runmake failed
| + exit 1
|
| cc1plus: error: include location "/usr/include/directfb" is unsafe for cross-compilation
| make: *** [out/Release/obj.target/app_base/ui/base/animation/animation.o] Error 1
| + die 'oe_runmake failed'
| + oefatal 'oe_runmake failed'
| + echo FATAL: 'oe_runmake failed'
| FATAL: oe_runmake failed
| + exit 1
Thanks
Yogesh
On Tuesday 08 February 2011 09:32 AM, embedded.yogesh wrote:
> On Tuesday 08 February 2011 12:05 AM, Gary Thomas wrote:
>> On 02/07/2011 11:23 AM, Darren Hart wrote:
>>> On 02/07/2011 04:51 AM, embedded.yogesh wrote:
>>>> On Monday 07 February 2011 05:45 PM, Gary Thomas wrote:
>>>>> On 02/06/2011 09:52 PM, yogesh lal wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I am new to poky, so don't know it will make any sense or not, but
>>>>>> can we build chromium browser using Poky ?
>>>>>
>>>>> What's your target architecture? Last I checked, only x86 and ARM
>>>>> are supported.
>>>>>
>>>>> It can be done, but it's certainly not for the faint of heart :-)
>>>>>
>>>>
>>>> I am working on X86 platform. Can you give some initial start up
>>>> where I
>>>> have to look ?
>>>
>>> Find and download the Chromium source, then have a look at the Poky
>>> Reference Guide for how to create an appropriate recipe, using
>>> recipes for projects with similar source layouts
>>> as examples.
>>>
>>> http://www.yoctoproject.org/docs/poky-ref-manual/poky-ref-manual.html
>>
>> Probably a lot easier to start with the OpenEmbedded recipe
>> since it already works. The biggest problem is that there
>> are a ton of dependencies, so you'll need to bring in those
>> recipes as well.
>>
>
> Thanks Gary Thomas and Darren Hart ,
>
> I am look in to poky-ref-manual and OpenEmbedded recipes :)
>
> ---
> Yogesh
next prev parent reply other threads:[~2011-02-21 5:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 4:52 chromium browser yogesh lal
2011-02-07 12:15 ` Gary Thomas
2011-02-07 12:51 ` embedded.yogesh
2011-02-07 18:23 ` Darren Hart
2011-02-07 18:35 ` Gary Thomas
2011-02-08 4:02 ` embedded.yogesh
2011-02-21 5:33 ` embedded.yogesh [this message]
2011-02-22 11:13 ` Richard Purdie
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=4D61F90D.606@gmail.com \
--to=embedded.yogesh@gmail.com \
--cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox