Re: [PATCH 2/3] build.sh: Install newly built packages

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

On 2018-02-01 11:09, 'Benedikt Niedermayr' via isar-users wrote:
> Am 01.02.2018 um 09:07 schrieb Alexander Smirnov:
>> Please take a look to dpkg class and to example-hello application. 
> 
> Ok,
> 
> but when I look into example-hello then I'm able to comprehend that, but
> 
> when I take look at example-raw which only inlcudes dpkg-raw then I
> can't see any possibility to build
> 
> the package out from its sources.
> 
> 
> So when including dpkg.bbclass then I'm able to build out from sources.
> 
> But when I also need to "debianize" my sources I have to include
> dpkg-raw, which in turn will overwrite the
> 
> dpkg_runbuild task.
> 
> I think the dpkg_runbuild of dpkg-raw should also call "sudo chroot
> ${BUILDCHROOT_DIR} /build.sh ${PP}/${SRC_DIR}" ?

There are currently three ways to build a package:

- the sources comes with debian/ control files
   -> inherit dpkg
- the sources are not debianized and you don't want to do that
   -> inherit dpkg-raw, build manually (if needed at all), define
      artifacts and let the raw class do that ad-hoc binary packaging
- the sources are not debianized, but your recipe can fill that gap
   -> inherit dpkg-base, provide a debian/ folder, overload
      dpkg_runbuild to trigger a debianized build

I'm going the last path with the upcoming custom kernel recipe.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux