From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/2] ISAR SDK image support
Date: Thu, 17 May 2018 09:47:26 +0200 [thread overview]
Message-ID: <20180517074726.GA7788@yssyq.radix50.net> (raw)
In-Reply-To: <20180516155653.29870-1-mosipov@ilbers.de>
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.
next prev parent reply other threads:[~2018-05-17 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 15:56 Maxim Yu. Osipov
2018-05-16 15:56 ` [PATCH v2 1/2] isar-bitbake: Add AUTOREV definition Maxim Yu. Osipov
2018-05-16 15:56 ` [PATCH v2 2/2] image: Add ISAR SDK package to create SDK from any rootfs image Maxim Yu. Osipov
2018-05-18 8:19 ` Henning Schild
2018-05-18 8:28 ` Henning Schild
2018-05-17 7:47 ` Baurzhan Ismagulov [this message]
2018-05-18 8:33 ` [PATCH v2 0/2] ISAR SDK image support Henning Schild
2018-05-18 11:01 ` Maxim Yu. Osipov
2018-05-22 8:26 ` Henning Schild
2018-05-22 10:43 ` Jan Kiszka
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=20180517074726.GA7788@yssyq.radix50.net \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
/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