From: Jan Kiszka <jan.kiszka@siemens.com>
To: Francesco <fdprnd@dave.eu>, isar-users@googlegroups.com
Subject: Re: questions about cross compilation and licence report
Date: Fri, 11 May 2018 15:52:22 +0200 [thread overview]
Message-ID: <7f45ad9b-27ae-82be-2726-d40994e62439@siemens.com> (raw)
In-Reply-To: <6d8b34ba-f8de-eed9-d06b-37a5db8ddd81@dave.eu>
On 2018-05-10 10:13, Francesco wrote:
> Hi All,
>
> I have a couple of general questions about isar.
> Is it possible to generate a report containing all the licences of the
> packages that are installed during the rootfs generation process?
I'm not aware of even a simple script for doing that. The reason might
be that the exact license compliance processes heavily depend on
company-internal regulations. For us, e.g., such an aggregation would
currently not be enough - without checking that what Debian reports is
complete and accurate. But that should not block working on such a
thing. My hope is that we will eventually be able to use Debian reports
directly as well.
>
> Perhaps some of you have already faced the problem of developing cross
> compiled applications.
> Since with isar is not possible to produce a yocto-like sdk, which is
> the suggested approach to develop cross compiled applications which use
> external libraries?
>
A simple SDK support (corresponding sysroot aggregation, cross-compiler
setup description) and also cross-building for recipes are WIP. I hope
we see some prototype soon.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-05-11 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 8:13 Francesco
2018-05-11 13:52 ` Jan Kiszka [this message]
2018-05-14 8:51 ` Henning Schild
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=7f45ad9b-27ae-82be-2726-d40994e62439@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=fdprnd@dave.eu \
--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