public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: daniel.sangorrin@toshiba.co.jp (Daniel Sangorrin)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support
Date: Tue, 11 Jul 2017 15:34:00 +0900	[thread overview]
Message-ID: <001f01d2fa0f$ae4a6410$0adf2c30$@toshiba.co.jp> (raw)
In-Reply-To: <71df6523-5844-01a2-8c67-d6ebc0a2a4f1@siemens.com>

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,
volume mount the project-x folder and manually set the proxy settings (for some reason using
build-args didn't work for me).
 
> 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.

Thanks,
Daniel

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

  reply	other threads:[~2017-07-11  6:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07  8:50 [cip-dev] Project-X (minimal root filesystem) : rewrite and renesas iwg20m board support Daniel Sangorrin
2017-07-07  9:00 ` Chris Paterson
2017-07-07 10:40 ` Jan Kiszka
2017-07-10 23:36   ` Daniel Sangorrin
2017-07-11  6:19     ` Jan Kiszka
2017-07-11  6:34       ` Daniel Sangorrin [this message]
2017-07-11  6:42         ` Jan Kiszka
2017-07-11  7:00           ` Daniel Sangorrin
2017-07-12  9:12             ` Jan Kiszka
2017-07-13  0:12               ` Daniel Sangorrin
2017-07-13  6:37                 ` Jan Kiszka
2017-07-13  7:39                   ` Daniel Sangorrin

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='001f01d2fa0f$ae4a6410$0adf2c30$@toshiba.co.jp' \
    --to=daniel.sangorrin@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.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