Re: [PATCH v3 06/16] sdk: Add support for adding self-defined sdk packages

[Jan Kiszka <jan.kiszka@siemens.com>]

On 15.10.20 23:51, Baurzhan Ismagulov wrote:
> On Wed, Oct 07, 2020 at 03:36:47PM +0200, Jan Kiszka wrote:
>> Fixed: test with "==", rather than "=". Cleaned up more around that.
> 
> Thanks, isar-apt.list is now available. However, when I enter the chroot, an
> attempt to run arm-linux-gnueabihf-gcc results in:
> 
> -bash: arm-linux-gnueabihf-gcc: command not found
> 

Checking... Nope, works fine here:

- echo 'SDK_INCLUDE_ISAR_APT = "1"' >> conf/local.conf
- bitbake -c populate_sdk mc:qemuarm-buster:isar-image-base
- sudo tar xJf
/work/build/tmp/deploy/images/qemuarm/sdk-debian-buster-armhf.tar.xz
- sudo sdk-debian-buster-armhf/mount_chroot.sh sdk-debian-buster-armhf/
- sudo chroot sdk-debian-buster-armhf/

root@566b0c868313:/# arm-linux-gnueabihf-gcc
arm-linux-gnueabihf-gcc-8.bin: fatal error: no input files
compilation terminated.

Please provide more details what you did.

> 
>> I'm all for adding relevant information, but this one does not qualify.
>> Checking for the toolchain being install was always completely pointless
>> in the context of an SDK that always has this pre-installed according to
>> our recipes.
> 
> Yes, it might be confusing in the context of SDK. The section is meant as a
> story and not a literal instruction. It tells the user that he can sudo apt-get
> install crossbuild-essential-armhf libhello-dev:armhf and build his application
> on the host with stock Debian, without any SDK. It describes the official

This section is part of the SDK, not the user manual. So the context is
not as broad as you describe it here.

> Debian build tooling and is certainly not limited to the chroot mode, while the
> SDK is a convenience offer so that developers famliar with Yocto can start
> right away before they learn Debian tools. Checking for the toolchain shows how
> stuff works rather than verifying that the recipes have done their job.
> 
> 
>> And since isar-apt is now a special case and SDK_INSTALL
>> will ensure that all required packages are already installed, the second
>> hint is also irrelevant for normal users. It is only for the case of
>> SDK_INCLUDE_ISAR_APT = 1 *and* SDK_INSTALL *not* listing self-built
>> devel packages needed for building applications.
> 
> Yes, so, it is a supported use case and must remain documented.

Then we need README generation - because all this only makes sense in
that non-default case. I don't see much value, though.

> 
> 
>> If you have other information that may help users with using the SDK in
>> chroot mode, feel free to add that on top.
> 
> I don't have new material to add. The existing wording is good enough for me.
> After the compiler is fixed, I'd be ready to apply the series while keeping the
> discussed section till we have a suitable replacement.

No, that section will not stay for the common case. I will add the
relevant parts in case SDK_INCLUDE_ISAR_APT = 1 and still drop the
irrelevant ones (toolchain check).

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux