[oe] [meta-browser] Modern Chromium with GN

[Otavio Salvador]

On Mon, Oct 23, 2017 at 9:06 AM, Raphael Kubo da Costa
<raphael.kubo.da.costa at intel.com> wrote:
> Trevor Woerner <twoerner at gmail.com> writes:
>
>> On Thu 2017-10-19 @ 06:24:11 PM, Raphael Kubo da Costa wrote:
>>> Raphael Kubo da Costa <raphael.kubo.da.costa at intel.com> writes:
>>> > Work on Chromium 62 has started, but updating is a bit slower now that
>>> > I'm trying to test GCC 5, 7, pyro and rocko.
>>>
>>> I've pushed a new branch called "chromium62". It's been test-built
>>> against Yocto's pyro (with GCC 5) and rocko (with GCC 7) for x86 and
>>> x86-64.
>>>
>>> Additional testing is appreciated!
>>
>> It looks like something in the chromium62 build is calling my native g++ and
>> expecting that this native g++ will be recent enough to support c++14:
>>
>>
>>       | g++ -MMD -MF base/base_paths.o.d
>>       | -I/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62/out_bootstrap/gen
>>       | -I/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62
>>       | -isystem/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/recipe-sysroot-native/usr/include
>>       | -O2 -pipe -DNO_TCMALLOC -D__STDC_FORMAT_MACROS -O2 -g0
>>       | -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS
>>       | -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions
>>       | -isystem/z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/recipe-sysroot-native/usr/include
>>       | -O2 -pipe -std=c++14 -Wno-c++11-narrowing -c
>>       | /z/chromium/crosswalk/build/tmp-glibc/work/x86_64-linux/gn-native/62.0.3202.62-r0/chromium-62.0.3202.62/base/base_paths.cc
>>       | -o base/base_paths.o
>>       | g++: error: unrecognized command line option ‘-std=c++14’
>
> Ouch :( That's a new kind of issue I was not expecting.

It needs to check if c++14 is really needed for GN to work. Better
would it depends on gn-native and it to be handled elsewhere.

>> [...]
>
>> Is there any way to intercept these calls and have it call OE's gcc-native
>> instead?
>
> Do you have an example of that being done in another recipe?

Hard. We don't build a native compiler.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750