[Buildroot] [PATCH 2/3] package/python-jailhouse: new package

[Yegor Yefremov]

On Mon, Jul 1, 2019 at 12:39 PM Carlo Caione <ccaione at baylibre.com> wrote:
>
> On 01/07/2019 08:04, Yegor Yefremov wrote:
> > Hi Carlo,
>
> Hi Yegor,
>
> >> --- /dev/null
> >> +++ b/package/python-jailhouse/python-jailhouse.mk
> >> @@ -0,0 +1,14 @@
> >> +################################################################################
> >> +#
> >> +# python-jailhouse
> >> +#
> >> +################################################################################
> >> +
> >> +PYTHON_JAILHOUSE_VERSION = 0.10
> >> +PYTHON_JAILHOUSE_SITE = $(call github,siemens,jailhouse,v$(JAILHOUSE_VERSION))
> >> +PYTHON_JAILHOUSE_LICENSE = GPL-2.0
> >> +PYTHON_JAILHOUSE_LICENSE_FILES = COPYING
> >> +
> >> +PYTHON_JAILHOUSE_SETUP_TYPE = setuptools
> >> +
> >> +$(eval $(python-package))
> >
> > Does python-jailhouse depend on jailhouse at run-time? I would just
> > make one package jailhouse and compile python-jailhouse if either
> > Python2 or Python3 is selected. So instead of 3 patches you can make
> > just one.
>
> You mean having one single package for both jailhouse and
> python-jailhouse in one single mk file? Can we practically achieve that
> since jailhouse is a generic package while I'm using $(eval
> $(python-package)) for python-jailhouse?

You'll probably have to mimic package/pkg-python.mk and invoke python
setup.py manually if Python/Python3 is selected. See
package/lirc-tools/lirc-tools.mk, but there autotools take care of
Python compilation stuff.

Yegor