On Apr 12, 2016, at 11:49 AM, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > A lot of projects simply aren't built in a way that would allow that. The > whole package (library, whatever) needs to be configured once with all the > options, and built once. sub ports for the additional features simply aren't > a option in main (most, I would bet) cases.
Do they build the same output with different features? Port A with and without +foo builds lib-A.dylib And not, Port A without +foo builds lib-A.dylib and with +foo builds lib-A.dylib & lib-A-foo.dylib? IIRC the subversion-bindings ports didn't initially have nice 'install' targets, so we manually cleaned up post-destroot so that they would just have the additional libs that were necessary. The actual 'build' ends up duplicating some build products that don't get installed for the bindings ports (because they're already installed by the main port) - but it's worth it to have everything "just work" for our end-users. -- Daniel J. Luke _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
