Skip to content

Conversation

@pitrou
Copy link
Member

@pitrou pitrou commented Jan 30, 2020

The binaries are installed using Chocolatey, which takes a bit of time (it's a 2+GB install...), but less so than recompiling Boost from scratch during the CMake build.

[skip appveyor]

@github-actions
Copy link

@pitrou
Copy link
Member Author

pitrou commented Jan 30, 2020

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we keep this step?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's useful to have system info in CI builds.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we update this when boost-msvc-14.1 is updated?
Can we detect this automatically?

Does this work?

diff --git a/.github/workflows/cpp.yml b/.github/workflows/cpp.yml
index abc3b8f4d..4cccbdfd0 100644
--- a/.github/workflows/cpp.yml
+++ b/.github/workflows/cpp.yml
@@ -185,7 +185,11 @@ jobs:
           submodules: true
       - name: Build
         shell: bash
-        run: ci/scripts/cpp_build.sh $(pwd) $(pwd)/build
+        run: |
+          boost_root="$(echo /c/local/boost_* | head -n1)"
+          export BOOST_ROOT="c:\\local\\$(dirname ${boost_root})"
+          export BOOST_LIBRARYDIR="${BOOST_ROOT}\\lib64-msvc-14.1"
+          ci/scripts/cpp_build.sh $(pwd) $(pwd)/build
       - name: Test
         shell: bash
         run: ci/scripts/cpp_test.sh $(pwd) $(pwd)/build

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I'll try it :-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did this:

  export BOOST_ROOT="$(ls -1 /c/local/boost_* | tail -n1)"
  export BOOST_LIBRARYDIR="${BOOST_ROOT}\\lib64-msvc-14.1"
  echo "BOOST_ROOT: ${BOOST_ROOT}"

and I got:

BOOST_ROOT: tools

:-O

I don't want to spend time debugging this (especially as Github Actions seems a bit slow today), so I'm gonna revert the change.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. I'll take it over as a follow-up task.

@pitrou pitrou force-pushed the ARROW-7726-download-boost-gha branch from 9060c3e to acb9383 Compare February 3, 2020 15:04
@pitrou pitrou force-pushed the ARROW-7726-download-boost-gha branch from acb9383 to eb5db8f Compare February 3, 2020 15:32
Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@kou kou closed this in 4b54997 Feb 3, 2020
@pitrou pitrou deleted the ARROW-7726-download-boost-gha branch February 4, 2020 00:15
@wesm
Copy link
Member

wesm commented Feb 4, 2020

I wonder why it's 2+GB, is it because of the static libraries I guess?

@pitrou
Copy link
Member Author

pitrou commented Feb 4, 2020

Not sure. I think it bundles all versions (debug, etc.) of the libraries.

kszucs pushed a commit that referenced this pull request Feb 7, 2020
The binaries are installed using Chocolatey, which takes a bit of time (it's a 2+GB install...), but less so than recompiling Boost from scratch during the CMake build.

[skip appveyor]

Closes #6325 from pitrou/ARROW-7726-download-boost-gha and squashes the following commits:

e877622 <Antoine Pitrou> Revert "Try a more flexible way of finding Boost"
eb5db8f <Antoine Pitrou> Try a more flexible way of finding Boost
d570649 <Antoine Pitrou> ARROW-7726:   Use boost binaries on Windows GHA build

Authored-by: Antoine Pitrou <[email protected]>
Signed-off-by: Sutou Kouhei <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants