Hi, I'm trying to build a Python 3 application which depends on some modules that are already packaged in OE for Python 2, but not for Python 3. Since OE currently has virtually no Python 3 module recipes, this makes me wonder what the best approach to create these recipes would be.
In most cases, I could just copy a Python 2 recipe, change the name from "python-foo" to "python3-foo", and replace "inherit distutils" with "inherit distutils3". However that would create a lot of duplication, and might turn into a maintenance nightmare. Do you have a suggestion what the right course of action would be? Move most of the recipes' content to .inc files that can then be included by both Python 2 and Python 3 recipes? Or maybe create a .bbclass that would build both versions from the same recipe? Is there any functionality already in place that would simplify this task? Dominic -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
