On 12 October 2016 at 09:31, Robert Yang <liezhi.y...@windriver.com> wrote:
> Its Makefile's do_install creates .pyc files for python3, now also > create them for python2 so that they will be recorded by manifest, and > can be cleaned correctly. So this is about autotools byte-compiling for python3 at install time and then something using those python modules with python2 during the build? I wonder if this is something that should/can be solved in a more generic way? Alternatively, is the xcbgen user something in oe-core and can we tell it to not use python2? - Jussi > Signed-off-by: Robert Yang <liezhi.y...@windriver.com> > --- > meta/recipes-graphics/xorg-proto/xcb-proto_1.12.bb | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/meta/recipes-graphics/xorg-proto/xcb-proto_1.12.bb > b/meta/recipes-graphics/xorg-proto/xcb-proto_1.12.bb > index 8bdca32..54988fc 100644 > --- a/meta/recipes-graphics/xorg-proto/xcb-proto_1.12.bb > +++ b/meta/recipes-graphics/xorg-proto/xcb-proto_1.12.bb > @@ -28,3 +28,11 @@ RDEPENDS_${PN}-dev = "" > RRECOMMENDS_${PN}-dbg = "${PN}-dev (= ${EXTENDPKGV})" > > BBCLASSEXTEND = "native nativesdk" > + > +do_install_append() { > + # Makefile's do_install creates .pyc files for python3, now also > create > + # them for python2 so that they will be recorded by manifest, and can > be > + # cleaned correctly. > + cd ${D}${libdir}/xcb-proto/xcbgen > + python -m py_compile *.py > +} > -- > 2.9.0 > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core >
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core