Re: questions about cross compilation and licence report

[Henning Schild <henning.schild@siemens.com>]

Am Fri, 11 May 2018 15:52:22 +0200
schrieb "Jan Kiszka" <jan.kiszka@siemens.com>:

> 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.

At the moment your two options would be:

1. derive an image from your real image, there you would add everything
you need to code/compile etc. i.e. install kde+eclipse+...
This one works fine for x86 but is not suitable for cross builds.

> require my-fancy-image.bb; IMAGE_PREINSTALL+="gvim build-essential"

2. extract the buildchroot after image creation and add
--sysroot=/path/to/isar/buildchroot to the FLAGS in your Makefiles and
prefix your toolchain with CROSS_ .
To get the libs in write a recipe with your build-deps. 
You should write a proper debianized recipe for your applications so
Isar will build them without leveraging the CROSS_ infrastructure you
use for development.

Henning

> Jan
>