On 11/09/2019 16:27, Alexander Kanavin wrote:
I have to say, the latter patch is rather ugly. It would be better to
split python3native class into two: python3native (just for running
scripts, does not depend on target python3), and python3target (for
actually obtaining information about the target configuration, does need
target python3). Until then, I'd just pull in target python, for
simplicity's sake (also there's one or two recipes where the same meson
problem happens).
Oh yes, the patch isn't pretty.
I was wondering how many recipes actually need the ability to run
nativepython getting information about target python. Splitting the
class, or having a toggle, was an idea I had too.
Ross
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
