On Dec 28, 2012, at 02:27, Vincent Habchi wrote: > I am refactoring the gmsh port which is somehow out of date and I also add > various variants to it, especially to remove the mesa dependency (with all > implied X11 ports). Futhermore, I’d like to add a +pythonXX variant to enable > python bindings: I thought about declaring gmsh +pythonXX both in CMake and > PythonXX PortGroups, but obviously they conflict in the way configure is > handled. > > Is there an elegant way to make both PortGroup work together without having > to rewrite all the Python PortGroup sugar?
Well the python portgroup is for making python module ports. It's not for adding +pythonXX variants to non-python ports. If the gmsh build system allows this without too much trouble, the nicest option would be if you could create pyXX-gmsh subports which could use the python portgroup. Or a standalone py-gmsh port using the python portgroup and sharing gmsh's dist_subdir. As for the conflict between the python and cmake portgroups, I'm guessing that's occurring because the python portgroup wants to turn off the configure phase, and the cmake portgroup wants to change the configure phase? Does simply adding "use_configure yes" work? If not, what problem are you seeing? _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
