You’ll probably need to build form source in either environment if you want to be sure of the deployment target. Both Homebrew and Macports are focused on running OS software for the current system, much less so for building baked libraries to run on other systems.
Dan Wilcox @danomatika https://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
On Oct 10, 2016, at 12:03 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Judging from the output of brew —env, there is a MACOSX_DEPLOYMENT_TARGET you should be able to set/override. Simplest way would be when running brew http://stackoverflow.com/questions/23338713/homebrew-how-to-permanently-override-homebrew-cc-homebrew-cxx-env-settings:
MACOSX_DEPLOYMENT_TARGET=10.6 brew …That, in combination with —build-from-source when installing packages, might give you want you need.
That could work, but then I'm back to building from source. (macports uses binaries for most stuff, btw.)
I'm happy to investigate further _if_ a homebrew dev says that they officially support installing this way. There's a similar way to change the deployment target for macports. But one of the devs told me that kind of compatibility isn't a design goal and they don't support doing that.
-Jonathan