[OE-core] how can i ask to keep all the generated "nativesdk" rpms?

Robert P. J. Day rpjday at crashcourse.ca
Thu Oct 20 10:31:07 UTC 2016


On Wed, 19 Oct 2016, Richard Purdie wrote:

> On Wed, 2016-10-19 at 17:34 -0400, Robert P. J. Day wrote:
> >   so, i'm home and on a different system about to do a build ...
> > refresh my memory, where are all those nativesdk rpms supposed to
> > show up? if memory serves, they were under
> > tmp/deploy/rpm/x86_64_linux. anything i should set before i
> > attempt a build?
>
> For SDKMACHINE="x86_64", the would appear in:
>
> tmp/deploy/rpm/x86_64_nativesdk/
>
> and SDKMACHINE="i686" in:
>
> tmp/deploy/rpm/i686_nativesdk/
>
> Switching SDKMACHINE might have been a trigger for one set
> disappearing, particularly on older versions. Which version was
> this? There were some bugs fixed in master/morty related to it.

  just for fun, i'm going to do a fresh build right now, involving:

* fresh "git pull" of poky
* MACHINE=mpc8315e-rdb
* bitbake core-image-minimal

  current state of poky (master branch)

$ git show
commit ef627ab364d52fe19994c94c1a78fbe21620a32c
Author: Joshua Lock <joshua.g.lock at intel.com>
Date:   Wed Oct 12 21:46:42 2016 +0100

    local.conf.sample.extended: remove RM_OLD_IMAGE
    ... etc ...

  that's it, no other customization other than selecting MACHINE and
pointing build at my local source mirror. and away we go ... and the
end result is, under tmp/deploy/rpm/:

$ ls -l
total 328
drwxr-xr-x. 2 rpjday rpjday   4096 Oct 20 05:54 all
drwxr-xr-x. 2 rpjday rpjday  40960 Oct 20 06:06 mpc8315e_rdb
drwxr-xr-x. 2 rpjday rpjday 286720 Oct 20 06:09 ppce300c3
$

should i have expected a nativesdk directory?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


More information about the Openembedded-core mailing list