Local testing of inclusion of Boost as a submodule has revealed some undesirable side effects: - all sources, documentation, etc. regardless of relevance to SciPy must be fetched - recursive submodule initialization can take quite a while (~10 minutes on my machine and internet connection) - lots of churn when running commands like `git status` Of course we will also need to see how this impacts the CI pipelines. This extra overhead may initially cause some timeouts. Another option that will alleviate some of these pains is to create a header only repo similar to this one: https://github.com/povilasb/boost-header-only. It could live in the SciPy github account and would be easy to update -- simply download the Boost tarball release and copy over the include directory only (or build a specific commit locally and do the same thing). It is more maintenance than simply checking out the latest tagged release of Boost and updating the submodules (adds an extra step of updating the header only repo), but it minimizes space and bandwidth usage. Thoughts? On Thu, Feb 18, 2021 at 3:01 AM Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Thu, Feb 18, 2021 at 3:45 AM Nicholas McKibben <nicholas.bgp@gmail.com> wrote:
Probably good to make sure that aarch64 build times remain relatively stable
Good point! Can this be checked via a PR to scipy-wheels?
Don't worry about this one, if compile time increase on other platforms is minor, it'll be fine for aarch64 too. We have limited TravisCI credits (actual status of that is a little unclear), so no need to burn them for this. We anyway should be moving CI providers for aarch64 at some point, probably to https://www.drone.io/
Cheers, Ralf
_______________________________________________ SciPy-Dev mailing list SciPy-Dev@python.org https://mail.python.org/mailman/listinfo/scipy-dev