On 2019-03-06 14:26, Kaz Kylheku (poky) wrote:
So I'm guessing this should be
FILES_${PN}-core_remove =
No dice. FILES_${PN}-core_remove = "${libdir}/python-2.7/encodings" does
not register anywhere. In the "bitbake -e" output, no _remove event
appears for FILES_python-core, and the image
On Wed, 6 Mar 2019 at 22:27, Kaz Kylheku (poky)
<442-103-8...@kylheku.com> wrote:
> Ah, okay; this is because it's been split into various sub-packages. So
> we have to operate on "-core".
> The .json manifest brings these into the "core" package:
>
> "${libdir}/python2.7/encodings",
>
On 2019-03-06 12:29, Burton, Ross wrote:
On Wed, 6 Mar 2019 at 20:14, Kaz Kylheku (poky)
<442-103-8...@kylheku.com> wrote:
So, the issues are now is that
FILES_${PN}_remove = "${libdir}/python2.7/encodings"
in fact does not work, as I believed.
Have a look at python.bb. Specifically:
PACKA
On Wed, 6 Mar 2019 at 20:14, Kaz Kylheku (poky)
<442-103-8...@kylheku.com> wrote:
> So, the issues are now is that
>
> FILES_${PN}_remove = "${libdir}/python2.7/encodings"
>
> in fact does not work, as I believed.
Have a look at python.bb. Specifically:
PACKAGES_remove = "${PN}"
There is no PN
On 2019-03-06 10:23, Richard Purdie wrote:
On Tue, 2019-03-05 at 18:28 -0800, Kaz Kylheku (poky) wrote:
How do we get Yocto to react to FILES changes, short of blowing away
the entire build tree?
Maybe related to this change:
http://git.yoctoproject.org/cgit.cgi/poky/commit/bitbake/lib/bb/dat
On Tue, 2019-03-05 at 18:28 -0800, Kaz Kylheku (poky) wrote:
> Hi,
>
> I'm working in a Yocto 2.5 environment.
>
> In my own layer, I added a bbappend targeting python which does this:
>
>FILES_${PN}_remove = "${libdir}/python2.7/encodings"
>
> Now this didn't take effect as I expected. I h
Hi,
I'm working in a Yocto 2.5 environment.
In my own layer, I added a bbappend targeting python which does this:
FILES_${PN}_remove = "${libdir}/python2.7/encodings"
Now this didn't take effect as I expected. I had to do a "bitbake -c
cleanall python" to rebuild the package.
In any case,
