* chromium browser
@ 2011-02-07 4:52 yogesh lal
2011-02-07 12:15 ` Gary Thomas
0 siblings, 1 reply; 8+ messages in thread
From: yogesh lal @ 2011-02-07 4:52 UTC (permalink / raw)
To: poky
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
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 ?
Thanks
[-- Attachment #2: Type: text/html, Size: 149 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: chromium browser
2011-02-07 4:52 chromium browser yogesh lal
@ 2011-02-07 12:15 ` Gary Thomas
2011-02-07 12:51 ` embedded.yogesh
0 siblings, 1 reply; 8+ messages in thread
From: Gary Thomas @ 2011-02-07 12:15 UTC (permalink / raw)
To: yogesh lal; +Cc: poky
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 :-)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: chromium browser
2011-02-07 12:15 ` Gary Thomas
@ 2011-02-07 12:51 ` embedded.yogesh
2011-02-07 18:23 ` Darren Hart
0 siblings, 1 reply; 8+ messages in thread
From: embedded.yogesh @ 2011-02-07 12:51 UTC (permalink / raw)
To: poky
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 ?
Thanks :)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: chromium browser
2011-02-07 12:51 ` embedded.yogesh
@ 2011-02-07 18:23 ` Darren Hart
2011-02-07 18:35 ` Gary Thomas
0 siblings, 1 reply; 8+ messages in thread
From: Darren Hart @ 2011-02-07 18:23 UTC (permalink / raw)
To: embedded.yogesh; +Cc: poky
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
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: chromium browser
2011-02-07 18:23 ` Darren Hart
@ 2011-02-07 18:35 ` Gary Thomas
2011-02-08 4:02 ` embedded.yogesh
0 siblings, 1 reply; 8+ messages in thread
From: Gary Thomas @ 2011-02-07 18:35 UTC (permalink / raw)
To: Darren Hart; +Cc: poky
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.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: chromium browser
2011-02-07 18:35 ` Gary Thomas
@ 2011-02-08 4:02 ` embedded.yogesh
2011-02-21 5:33 ` embedded.yogesh
0 siblings, 1 reply; 8+ messages in thread
From: embedded.yogesh @ 2011-02-08 4:02 UTC (permalink / raw)
To: poky
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: chromium browser
2011-02-08 4:02 ` embedded.yogesh
@ 2011-02-21 5:33 ` embedded.yogesh
2011-02-22 11:13 ` Richard Purdie
0 siblings, 1 reply; 8+ messages in thread
From: embedded.yogesh @ 2011-02-21 5:33 UTC (permalink / raw)
To: poky
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: chromium browser
2011-02-21 5:33 ` embedded.yogesh
@ 2011-02-22 11:13 ` Richard Purdie
0 siblings, 0 replies; 8+ messages in thread
From: Richard Purdie @ 2011-02-22 11:13 UTC (permalink / raw)
To: embedded.yogesh; +Cc: poky
Hi,
On Mon, 2011-02-21 at 11:03 +0530, embedded.yogesh wrote:
> 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
Its accessing parts of the build system (/usr/include) and the compiler
is turning warnings into errors and failing. You need to fix the build
to use the sysroot for cross compiling and not to look at the build
system.
Cheers,
Richard
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2011-02-22 11:13 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2011-02-22 11:13 ` Richard Purdie
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox