From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6556209687865327616 X-Received: by 2002:a19:5014:: with SMTP id e20-v6mr1833465lfb.9.1526632414969; Fri, 18 May 2018 01:33:34 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a19:d7db:: with SMTP id q88-v6ls937519lfi.10.gmail; Fri, 18 May 2018 01:33:34 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoxAY7JkqH9zGI0blG8vcjZPSV6/7cgFuJACalvE9yN9x8yTDaOuUqg8uw6TkeGJH6UeAOE X-Received: by 2002:a19:d204:: with SMTP id j4-v6mr1802044lfg.41.1526632414507; Fri, 18 May 2018 01:33:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526632414; cv=none; d=google.com; s=arc-20160816; b=dV4ihQHvCoXYjrc2S9Dmx9S8LjM/YD1gpCO4JrELyZlaGYS+K/JG8suUNH8opevJ02 Rqi1EiQsMwlMloB3HtPGk6E5nYb8NYXdkgkfCxSc943+kXDNJoC/Eogfl97+kRqq6k7c qHmpayeHmPIOHYUpWQUUCPvNxdCZpcuDC5gtLVWEUsPSdSzoGT2z8RacJAMi0x5zBmoF vi5oVDrl6hztBBpAyfdss1eltKqLqtZFWqYPF4Pa+F0ClJZ4WGrAKndX2JkjdoRsRuuH K1w4QC9f1THkctp7uqo8QZTtHrM0t3upGqqHQimeWvz0oMUIweFl1ChS0vnwnZs6Qc7B stRQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:arc-authentication-results; bh=k6iNGa0br/GNFYbPtZpc6vpZyxKliPnvGEFxqSFJY6o=; b=OS+FIpNkkjwE5/K5L0gT5xoAMaN8/LD5UP6LpLI6dvglQ6Vs1bqurnlUbinj4BCzlZ /T72jc5fPQyzAS5+yW4oOpatA97r6hxn9SKplL9ku+7FsQKMFD3Su7DHa3pe+NWf0jUH JUVwUtH0Bi7uHgjsERZ4F8E/D9n/jiOZJddoCE8cfgbXOXwP01XRhcNxE9TuKOk/2fgX +mbi3G32txwXCD1YGm/0MUcoqbaEgdZfZStaZ4MBMGF975S5alwp1Jk08iYcWLC4AZQy /5c0Zrr14YtHpQZQcS2svJfe1C7Hc1IzVSL6mdZsaL2oQGqPLLhiufXrP33hc+E6Umn0 S36g== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id y205-v6si267920lfa.0.2018.05.18.01.33.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 May 2018 01:33:34 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w4I8XXUV003882 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 18 May 2018 10:33:33 +0200 Received: from md1pvb1c.ad001.siemens.net (md1pvb1c.ad001.siemens.net [139.25.68.40]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id w4I8XXnp015824; Fri, 18 May 2018 10:33:33 +0200 Date: Fri, 18 May 2018 10:33:33 +0200 From: Henning Schild To: "Maxim Yu. Osipov" Cc: Subject: Re: [PATCH v2 0/2] ISAR SDK image support Message-ID: <20180518103333.5752a6f7@md1pvb1c.ad001.siemens.net> In-Reply-To: <20180516155653.29870-1-mosipov@ilbers.de> References: <20180516155653.29870-1-mosipov@ilbers.de> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-TUID: EEOfzlm3on08 Am Wed, 16 May 2018 17:56:51 +0200 schrieb "Maxim Yu. Osipov" : > Hello everybody, > > Please ignore previous patch series. > > This series introduces ISAR SDK image support. Thanks for looking into that! As i explained here https://groups.google.com/forum/#!topic/isar-users/bxmZQD8sSDQ There are two general ways to prepare an SDK. The image+devtools and the "--sysroot" of buildchroot way. You have implemented image+devtools which is only practical for non qemu-user-static setups ... basically just for x86 targets. While it will work for arm(64) on x86 you will end up with a horribly slow SDK. Horribly slow is OK for building the image with Isar, not for the fast turn-around you are looking for as a developer. What should be done instead is extracting the buildchroot and using it from the outside with "--sysroot", add example for make, CMake, eclipse And maybe creating an x86 Debian rootfs with the cross compiler that contains all that. Henning > In order to create ISAR SDK image just add package isar-sdk into > variable IMAGE_INSTALL in bitbake's conf/local.conf and fireup the > ISAR image build. > > When build is done, perform the following steps: > > 1) Copy host's hostname and resolv.conf into resulting rootfs: > > For example, > > sudo cp /etc/hostname > $HOME/isar/src/build/tmp/work/debian-stretch-amd64/isar-image-base/rootfs/etc > sudo cp /etc/resolv.conf > $HOME/isar/src/build/tmp/work/debian-stretch-amd64/isar-image-base/rootfs/etc > > 2) Mount the following directories in chroot by passing resulting > rootfs as an argument to the script mount_chroot.sh: > > $ cat mount_chroot.sh > #!/bin/bash > sudo mount /tmp $1/tmp -o bind > sudo mount proc $1/proc -t proc -o nosuid,noexec,nodev > sudo mount sysfs $1/sys -t sysfs -o nosuid,noexec,nodev > sudo mount devtmpfs $1/dev -t devtmpfs -o mode=0755,nosuid > sudo mount devpts $1/dev/pts -t devpts -o gid=5,mode=620 > sudo mount tmpfs $1/dev/shm -t tmpfs -o rw,seclabel,nosuid,nodev > > $./mount_chroot.sh > $HOME/isar/src/build/tmp/work/debian-stretch-amd64/isar-image-base/rootfs Should that helper not be part of the patch series? > 3) chroot to isar SDK rootfs: > > $sudo chroot > $HOME/isar/src/build/tmp/work/debian-stretch-amd64/isar-image-base/rootfs > > 4) In chroot change user to 'builder', cd to directory isar and start > the isar image generation as usual. > > For example, > > root@tiberius:/# su - builder > builder@tiberius:~$ cd isar/ > builder@tiberius:~/isar$ . isar-init-build-env ../build/ > builder@tiberius:~/build$ bitbake > multiconfig:qemuamd64-stretch:isar-image-base > > > Kind regards, > Maxim. > > Alexander Smirnov (1): > isar-bitbake: Add AUTOREV definition > > Maxim Yu. Osipov (1): > image: Add ISAR SDK package to create SDK from any rootfs image. > > meta-isar/recipes-core/images/isar-image-sdk.bb | 9 ++++++ > meta/conf/isar-bitbake.conf | 2 ++ > meta/recipes-devtools/isar-sdk/files/README | 2 ++ > meta/recipes-devtools/isar-sdk/files/postinst | 21 +++++++++++++ > meta/recipes-devtools/isar-sdk/isar-sdk.bb | 42 > +++++++++++++++++++++++++ 5 files changed, 76 insertions(+) > create mode 100644 meta-isar/recipes-core/images/isar-image-sdk.bb > create mode 100644 meta/recipes-devtools/isar-sdk/files/README > create mode 100644 meta/recipes-devtools/isar-sdk/files/postinst > create mode 100644 meta/recipes-devtools/isar-sdk/isar-sdk.bb >