Fix for issue 675

[mborland]

Fixes for #675. Allows for switching of BOOST_MATH_HEADER_DEPRECATED based on standalone context. Fixes behavior of standalone implementation.

[NAThompson]

Ready to go?

[mborland]

Ready to go?

Yes; this is good.

[jzmaddock]

Merging. Do we need to run the new test in standalone mode as well?

[thesamesam]

Thanks both. This indeed resolves the issue downstream for us in Gentoo. Cheers for the quick fix!

[NAThompson]

@jzmaddock : I want to do a new standalone release upon resolution of #677 ; do we have a good CI solution for testing our standalone releases?

[jzmaddock]

We would need to merge to master, and then just check that the CI run on master is clean.

[mborland]

@jzmaddock : I want to do a new standalone release upon resolution of #677 ; do we have a good CI solution for testing our standalone releases?

None of the current tests in the CI battery define BOOST_MATH_STANDALONE. I can open a PR for a new YAML file that runs against a different branch say standalone_master. That way you could just run it periodically instead of every time something is committed to develop. Currently the only thing that is tested in standalone mode is the compile tests using CMake. Thoughts?

[NAThompson]

Our CI suite is already pretty expensive. Maybe one configuration on each merge request, and then a big run on master or standalone_master.

We should probably see how @jzmaddock feels about having the standalone a bit out of sync with the Boost release cadence.