[yocto] Compiling meta-browser ==>chromium ? cleaning ?

[Riko Ho]

drwxrwxr-x 5 bianchi77 bianchi77 4.0K Jun 14 14:31 .
drwxrwxr-x 3 bianchi77 bianchi77 4.0K Jun 12 15:50 ..
drwxrwxr-x 2 bianchi77 bianchi77 4.0K Jun 12 15:50 cef3
-rw-rw-r-- 1 bianchi77 bianchi77 2.7K Jun 12 15:50 cef3_280796.bb
drwxrwxr-x 4 bianchi77 bianchi77 4.0K Jun 12 15:50 chromium
*-rw-rw-r-- 1 bianchi77 bianchi77 1.2K Jun 12 15:50 chromium_54.0.2810.2.bb*
-rw-rw-r-- 1 bianchi77 bianchi77  11K Jun 12 15:50 chromium-browser.inc
-rw-rw-r-- 1 bianchi77 bianchi77 4.6K Jun 12 15:50 chromium.inc
-rw-rw-r-- 1 bianchi77 bianchi77 2.2K Jun 12 15:50 
chromium-wayland_53.0.2785.143.bb
drwxrwxr-x 8 bianchi77 bianchi77 4.0K Jun 12 15:50 files

is this one ? *chromium_54.0.2810.2.bb ?

Thanks
*
On 21/06/17 10:28, Khem Raj wrote:
> add it to chromium recipe itself if you dont have a bbappend for it.
>
> On Tue, Jun 20, 2017 at 9:53 PM, Riko Ho <antonius.riko at gmail.com> wrote:
>> Ok, thanks a lot for the parameter idea, where will I put that ? local.conf,
>> bblayers.conf ?
>>
>>
>> On 20/06/17 13:08, Khem Raj wrote:
>>
>> On Mon, Jun 19, 2017 at 8:32 PM, Riko Ho <antonius.riko at gmail.com> wrote:
>>
>> My memory is 8Gb and swap 8Gb, 8 cores i7, may be a homemade cluster can
>> help ?
>>
>> add something like
>>
>> EXTRA_OEGYP_prepend = " -Dcomponent=shared_library
>> -Dremove_webcore_debug_symbols=1 -Dfastbuild=1 "
>>
>> and see if that helps.
>>
>> I compiled firefox and it worked well, but still wondering why chromium
>> didn't work.
>>
>>
>> On 20/06/17 04:01, Khem Raj wrote:
>>
>> On Mon, Jun 19, 2017 at 7:21 AM, Jacobo Aragunde Pérez
>> <jaragunde at igalia.com> wrote:
>>
>> On 18/06/17 20:10, Gunnar Andersson wrote:
>>
>> Riko Ho <antonius.riko at gmail.com> wrote:
>>
>> Hello Everyone,
>>
>> I tried to compile chromium but never succeeded, took me already 12
>> hours and stopped on 99%, I used bitbake for doing it,
>>
>> Not sure what would cause it to just stop and it could have been some
>> temporary glitch?   Maybe you want to provide some logs of your build if
>> Martin's reference does not help.
>>
>> Just a heads-up, if it stopped at 99% it probably was in the linking
>> phase (you can check the logs under
>> tmp/work/$arch/chromium-wayland/$version/temp/log.do_compile to be
>> certain). This phase has a very high RAM demand, you could even need to
>> temporarily increase your swap space to go past that point.
>>
>> linker takes a whole lot of memory here, if you have < 8G of RAM
>> its likely to fail with out of memory errors. Can you check your dmesg
>> and see if there were such errors in there
>>
>> Best,
>> --
>> Jacobo Aragunde
>> Software Engineer at Igalia
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>> --
>>
>> /*******/
>> Sent by Ubuntu LTS 16.04,
>> 谢谢,
>> Regards,
>> Riko Ho
>> /*******/
>>
>>
>> --
>>
>> /*******/
>> Sent by Ubuntu LTS 16.04,
>> 谢谢,
>> Regards,
>> Riko Ho
>> /*******/

-- 
*

/*******/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/*******/

*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20170621/fc223d21/attachment.html>