On Wed, Sep 27, 2017 at 3:17 PM, Tom Rini <tr...@konsulko.com> wrote: > On Wed, Sep 27, 2017 at 10:14:51PM +0000, Khem Raj wrote: >> On Wed, Sep 27, 2017 at 2:52 PM Tom Rini <tr...@konsulko.com> wrote: >> >> > On Wed, Sep 27, 2017 at 02:01:43PM -0700, Khem Raj wrote: >> > > On Wed, Sep 27, 2017 at 10:00 AM, Tom Rini <tr...@konsulko.com> wrote: >> > > > With RSS we need to ensure that when making a bmap image that the >> > > > python3 that we created is found via /usr/bin/env rather than the host >> > > > python3. Otherwise we're relying on the build host to have bmaptool >> > > > support installed. >> >> Who is staging python3 native here may be that's where it could be added > > What do you mean? Adding whatever.bmap to IMAGE_FSTYPES is valid and > how you get the bmap file for the whatever image type. bmap-tool-native > is correctly inherit'ing python3native which is why it's staged > correctly. It's just that images aren't adding the EXTRANATIVEPATH > that's required because nothing is telling them that bmap requires it.
hmm, I see, I wonder if these paths should be added unconditionally. During image build. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
