Fixes #70 by activating the proper environment on a macOS machine

This MR proposes the addition of activation/deactivate scripts to bob-devel to tackle the missing setup of variables required to compile packages on a mac machine.

These are the variables which are activate/deactivated:

• MACOSX_DEPLOYMENT_TARGET (set to 10.9 by default)
• CONDA_BUILD_SYSROOT (which gets incorrectly set to the latest SDK path)
• SDK_ROOT, to the same value of CONDA_BUILD_SYSROOT

added 5 commits

• 708d1f65...e16f1e8b - 4 commits from branch master
• ae37e0e9 - [bob/beat-devel] Fixes #70 (moved) by activating the proper environment on a macOS machine

Compare with previous version

@andre.anjos as far as I remember, we decided not to give this job to bob-devel.

You'll have to remember me why not...

Is this needed for local development or builds on the CI?

Eventually - it depends on how the CI is setup. If you have a better idea where to place these "activation" scripts, please suggest.

Both local and CI, that depends on the machine setup. This patch just guarantees the setup is correct.

I don't think this is the right place. To expose variables during CI builds, we have conda_build_config.yaml in bob.devtools. For local development, you can copy over these activation scripts to the new conda env when it's created using bdt create.

So - why doesn't the variables in conda_build_config.yaml get correctly set on the runtime?

they are exposed when you run conda build

closed