[cip-dev] Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support

[jan.kiszka@siemens.com (Jan Kiszka)]

On 2017-07-11 08:34, Daniel Sangorrin wrote:
> Hi Jan,
> 
>> -----Original Message-----
>> From: Jan Kiszka [mailto:jan.kiszka at siemens.com]
>> Sent: Tuesday, July 11, 2017 3:20 PM
>> To: Daniel Sangorrin; cip-dev at lists.cip-project.org
>> Cc: kas-devel
>> Subject: Re: [cip-dev] Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
>>
>> On 2017-07-11 01:36, Daniel Sangorrin wrote:
>>>> Btw, instead of having yet another setup.sh, you may want to have a look
>>>> at kas [2]. There is no release yet (next week, hopefully), but it is
>>>> fairly mature. Moreover, you can build inside Docker, removing most of
>>>> the host dependencies. We are using this now with both Yocto and Isar
>>>> projects, often in layered ways [3] that enable reuse.
>>>
>>> Yesterday I managed to build the qemux86-64 meta layer using the following
>>> kas project configuration. Could you check it please?
>>>
>>> https://gitlab.com/cip-playground/project-x/commit/de611ae06040f6e426d3c5d1b77eb20b4af31a19
>>
>> Looks good. You should just set version to 0.10 and use yesterday's
>> release. You can pull the corresponding docker image from
>> https://hub.docker.com/r/kasproject/, and there should be a pip package
>> as well soon.
> 
> That was fast. I was using the next branch and built the Dockerfile included in kas.
> 
> I had to create a daemon.json to set overlay2 as the storage driver, pass the USER_ID variable,

We should probably suggest to call "USER_ID=$(id -u) docker run ..." -
it there a way to achieve this in an easier way? Still learning all this
docker stuff.

> volume mount the project-x folder and manually set the proxy settings (for some reason using
> build-args didn't work for me).

Hmm, they should, I'm using them for builds all the time (along with
corresponding settings for the docker daemon).

>  
>> Does it still make a difference to set BB_NUMBER_THREADS and
>> PARALLEL_MAKE? I'm seeing full CPU usage without it as well. I'm always
>> looking for reasonable defaults we can set (?=) from kas automatically.
>> BB_DISKMON_DIRS should likely be included, I was adding it as well already.
> 
> You know better than me ;)
> I just checked the latest ref manual and apparently OE automatically sets them up.

Ah, good to know. The parallel things, or even also DISKMON?

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux