Android compile flags leaking into dependencies

I wasn't sure how to name this one.

Environment: Compiling Android libraries on OSX

harfbuzz 1.4.4-ft has a dependency on ragel-6.9 on the HOST system.

CXXFLAGS and such are exported in the main mason.sh file. They retain their values when we begin compiling the dependency in mason_prepare_compile.

The android specific compile flags are being sent through as I try to compile ragel for OSX, which causes configure to fail.

I think there's also going to be a future issue here; any changes made to CXXFLAGS while building the dependencies will pollute the original library.

Having this be the order of events might fix it
mason_prepare_compile
export CXXFLAGS=...
mason_compile

If mason_prepare_compile needs those flags in some cases, maybe dependency resolution needs to be an explicit step beforehand.
mason_prepare_dependencies
export CXXFLAGS=...
mason_prepare_compile
mason_compile

Start in mason.sh at mason_prepare_compile and trace how the harfbuzz dependency invokes ragel-6.9 on the host. Reproduce the Android library build on OSX, then verify that host dependencies do not receive Android-specific flags and that dependency changes do not leak into the original library build.