swig-python and python{24,25,31,32}

Michael Dickens michaelld at macports.org
Mon Jan 5 10:45:04 PST 2015

One issue with how SWIG is split up is that much of the wrapping code
logic is built in to the binary provided by "swig". Installing
"swig-python" just installs the headers & related data files used by
SWIG (which are necessary, but not sufficient). I'm not sure if Python
needs to be available during the build of SWIG itself (as a dependency),
but it might. Ditto for the other sub-ports, I'm guessing. Thus, while I
like the idea of the split, I'm guessing that the reality is that it
works because the dependencies are already installed before SWIG is
built rather than because the subports' dependencies are being honored
during each's build. Just a guess. Either way, the ports do seem to work
for most folks, so I'm inclined to leave them as is beyond removing
"python_select" as that ports' dependency. - MLD

On Sun, Jan 4, 2015, at 10:16 PM, Lawrence Velázquez wrote:
> I freely admit that I have no idea how SWIG works or how other software
> uses it. I just noticed that swig-python depends on python_select instead
> of any particular Python port, which is rather odd at first glance. If
> that doesn't actually cause any issues, so much the better.

More information about the macports-dev mailing list