SCons, the Python-based build system, tries to isolate itself from the user’s environment as much as possible, so that one developer’s weird environment variables don’t lead to an irreproducible build. This is great until you want to use tools from places that SCons doesn’t think are standard, in which case you can make use of its site_scons extension mechanism to make them standard.
In this case, I’m using Homebrew. Homebrew normally installs into
/usr/local. I think this default is completely mental, because
/usr/local is the Balkans of Mac software packaging: routinely invaded and full of land mines. I’ve installed Homebrew into
/opt/homebrew, where it’s safe from having parts overwritten at random by unmanaged package installers. For Make builds, I’ve included these lines at the end of my .zshrc to make Homebrew components available:
export PATH="/opt/homebrew/bin:$PATH" export CFLAGS='-I/opt/homebrew/include export LDFLAGS='-L/opt/homebrew/lib'
For SCons, I’ve created the file
$HOME/.scons/site_scons/site_init.py to modify the Environment object used by SCons subprocesses:
site_init.py decorates the Environment initializer to always add Homebrew to the
PATH, and now I have binaries like
sdl-config available. (SCons has support for parsing the flags emitted by those config programs.)
This should extend to
LDFLAGS, except that they’re most likely strings instead of lists.
The end result is that I can assume that any SCons build on my system will have access to libraries and tools installed through Homebrew.