[Buildroot] [RFC] package/python-mako: build host-python-mako as python3 module for mesa3d build.
romain.naour at smile.fr
Sat Apr 13 17:10:43 UTC 2019
Le 13/04/2019 à 18:54, Thomas Petazzoni a écrit :
> Hello Romain,
> On Sat, 13 Apr 2019 18:46:06 +0200
> Romain Naour <romain.naour at smile.fr> wrote:
>> But adding python3 on the target in order to have a python3 module
>> on the host is not nice.
>> To build host-python-mako as python3 module we can add this line
>> in pyhon-mako package:
>> HOST_PYTHON_MAKO_NEEDS_HOST_PYTHON = python3
>> But python mako is not available anymore for python2 interpreter.
>> The problem is more global, how can we build the same python
>> module for python2 and/or python3 on the host ?
> We can't :-)
My issue would be solved if we can do that :p
>> Mako module is also used by gnuradio build system and building
>> this module for python3 for mesa3d can eventually break the build of
>> gnuradio when the python interpreter on the host is python2
>> (to be tested).
> Indeed, your patch would break situations where mesa3d is enabled, but
> another package needs host-python-mako for python2 (and not python3).
Indeed it break gnuradio:
-- Configuring VOLK support...
-- Build type set to Release.
-- Found PythonInterp: output/host/bin/python2 (found suitable version "2.7.15",
minimum required is "2")
-- Python checking for python >= 2.7
-- Python checking for python >= 2.7 - found
-- Python checking for mako >= 0.4.2
-- Python checking for mako >= 0.4.2 - not found
-- Python checking for six - python 2 and 3 compatibility library
-- Python checking for six - python 2 and 3 compatibility library - found
CMake Error at volk/CMakeLists.txt:88 (message):
Mako templates required to build VOLK
> We solved this problem for python-setuptools by having
> host-python-setuptools and host-python3-setuptools as separate
> packages. It's not great, but we don't have any other good solution for
> this at the moment I believe.
The problem is that mesa3d is not a python package :)
See the check is mesa build system:
> Alternatively, perhaps for host Python modules we should always install
> them for both host-python and host-python3 (if both are enabled, of
> course). The gotcha is that since we don't have any Config.in options
> for host packages, how can we know if host-python and/or host-python3
> are enabled ?
I don't know... I need to dig deeper into this issue ;)
More information about the buildroot