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] Status of cip-core
Date: Mon, 23 Oct 2017 18:38:25 +0900	[thread overview]
Message-ID: <003901d34be2$acfa4010$06eec030$@toshiba.co.jp> (raw)

Hi all,

I have updated the cip-core quickstart instructions:
Ref: https://wiki.linuxfoundation.org/civilinfrastructureplatform/cip-core-quickstart

I have checked that they work for iwg20m and bbb. They should work for qemu and
cyclonev as well, but building targets takes a long time so I couldn't finish it today.

Additionally, I have upgraded cip-core to morty and KAS files to 0.13.0.
# now jethro (legacy) files are on their own branch, and morty (next release) is on the master branch

You can test the morty version as follows:
host$ git clone https://gitlab.com/cip-project/cip-core.git
host$ docker run -v $PWD/cip-core:/cip-core -e USER_ID=`id -u $USER` -e http_proxy=$http_proxy -e https_proxy=$https_proxy -e NO_PROXY="$no_proxy" -it kasproject/kas:0.13.0 sh
docker$ cd /cip-core/deby/poky/
docker$ kas build --target core-image-minimal meta-cip-iwg20m/kas-iwg20m.yml
[Alt] kas build --target core-image-minimal meta-cip-bbb/kas-bbb.yml

Current issues:
- KAS is using a single the same "build" folder for all targets, and this causes conflicts.
Until I figure out how to specify the name of the build folder, please delete the build/tmp
folder before building each target.
Jan: what is KAS_WORK_DIR in http://kas.readthedocs.io/en/latest/userguide.html#environment-variables?
- modules.tgz is not generated for iwg20m (for bbb it is): I have to investigate why but I think 
it is not a big problem since they are included in the file system images. Probably the reason
is just that shmobile_defconfig has modules disabled.
- B at D: there are some slight changes needed so I will send an updated version of the patches.

Cheers,
Daniel







 

             reply	other threads:[~2017-10-23  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23  9:38 Daniel Sangorrin [this message]
2017-10-23 18:23 ` [cip-dev] Status of cip-core Chris Paterson
2017-10-24  5:17   ` Daniel Sangorrin
2017-11-09 10:11     ` Chris Paterson
2017-11-10  7:35       ` Binh Thanh. Nguyen
2017-10-27 12:57 ` Daniel Wagner
2017-10-30  0:20   ` Daniel Sangorrin
2017-10-30  9:22     ` Daniel Wagner

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='003901d34be2$acfa4010$06eec030$@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