From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6556209687865327616 X-Received: by 2002:a9d:4292:: with SMTP id r18-v6mr3166352ote.30.1526543252622; Thu, 17 May 2018 00:47:32 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a9d:1f1c:: with SMTP id x28-v6ls3048300otd.14.gmail; Thu, 17 May 2018 00:47:32 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqCHCMiZGAbiBQx2Tqj7l3NzTZNlDDoQm2cBqXyMoclI3YNFQvwcZtj2lxxC20KWgfpHrUX X-Received: by 2002:a9d:e22:: with SMTP id c31-v6mr3024913otc.53.1526543252166; Thu, 17 May 2018 00:47:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526543252; cv=none; d=google.com; s=arc-20160816; b=s+KLwGx19PKXxADQrecjaF6BVbs1ZfUirrdIaQX7mvHf3Rtyn6r6mLz6H4WkMAwnch gmkf/d4t6sKE/FWRSPnc+qhUwYc4u5zw0XOGdyl99kxM/WZhXYH4f1MXXFI1YG+vybYV wlc9ylXLu9+w8RWUgbmF2Y6dZRLZhkgMYvkuai5kMP15w4hxM44Y6EUv1GAU5JvzCml/ RmJlBnr7aKUw3WK5QwmClx5sHjW8MSbK1CfkWiRciPZZ5vaE+zQEYYOiVlIgeKJUjMWR GIiLC/Gihakq/MPiRfzNjrB8b1YsouqT14vDXlysEs8AbW8jv5bESLqvcOPzHiD1WMnN traw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date :arc-authentication-results; bh=iGpMCH1R7SfzUmV13LwB015apA97wCZX+XhqSRaquog=; b=wPAgY5mLIdUzPVYQGwopp+O4k4f7hKHciA9bKZSsrH2yaALgvgDw0aPCnHBe0jzyZn ABp191TuxTkQyfvzUVX4eyYmAmjhLQyVZRwFJQzIetVRgPHfFV3uV+Wv3P2GzsRlFRsp zgNSGfYJdveBdOnz909vDzX57qPuAxSh/tJdR1Dfoz53ZZ9W6kIjxiZwf9DKI+3zM2UG jQ9y0x/+BJ6nFpz+MnQvXvSw3WsuG9u2y/MI6aSBxKF/xyddmpeyc5l6CuszTAAswPcz XA8ZpgBM7wk/y8qXerIYWlZyUrr6GTCzJYLcR9PeIMB//rL+8X2xfqxKUteYgIo7kpXk D44Q== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from aqmola.ilbers.de (aqmola.ilbers.de. [85.214.62.211]) by gmr-mx.google.com with ESMTPS id n5-v6si464717otk.5.2018.05.17.00.47.31 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 00:47:31 -0700 (PDT) Received-SPF: neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.62.211; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.62.211 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.radix50.net (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by aqmola.ilbers.de (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w4H7lSnN019943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 17 May 2018 09:47:29 +0200 Received: from yssyq.radix50.net (localhost [127.0.0.1]) by yssyq.radix50.net (8.14.4/8.14.4/Debian-8) with ESMTP id w4H7lQRv008232 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 17 May 2018 09:47:26 +0200 Received: (from ibr@localhost) by yssyq.radix50.net (8.14.4/8.14.4/Submit) id w4H7lQHU008231 for isar-users@googlegroups.com; Thu, 17 May 2018 09:47:26 +0200 Date: Thu, 17 May 2018 09:47:26 +0200 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Subject: Re: [PATCH v2 0/2] ISAR SDK image support Message-ID: <20180517074726.GA7788@yssyq.radix50.net> Mail-Followup-To: isar-users@googlegroups.com References: <20180516155653.29870-1-mosipov@ilbers.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180516155653.29870-1-mosipov@ilbers.de> User-Agent: Mutt/1.5.23 (2014-03-12) X-TUID: hgqta5kmQmef Hello Maxim, On Wed, May 16, 2018 at 05:56:51PM +0200, Maxim Yu. Osipov wrote: > Please ignore previous patch series. Your mails landed in spam, so I've deleted the previous mails to save people's time. > This series introduces ISAR SDK image support. Thanks. Could you please document this in the manual? With this implementation, one can qemu or chroot into the SDK and build artifacts (e.g., isar-image-base) in the native (e.g., armhf) buildchroot. The workflow looks like this: 1. System integrator prepares his build host, builds the system image and the SDK, and distributes them. 2. Developers flash the image to the target and use SDK to develop the application, and either: 1. Build new images and flash them, or 2. Build hello.deb and install it to the target manually. In this way, the current SDK: 1. Removes the necessity to prepare developer's build hosts. 2. Is usable on non-Debian hosts. 3. Provides downloads. @Jan: Do I understand your idea correctly: The SDK should contain a cross-compiler for the developers to build their applications? Or is this thought as a second step, when Isar is able to build packages in crossbuildchroot (or however we call it)? With kind regards, Baurzhan.