Skip to content

[CI][Python] CMakeLists detects ccache but not sccache #50996

Open

Description

@pitrou

Describe the enhancement requested

PyArrow's cmake setup should detect sccache just like the C++ one does.

This would make some Python Crossbow builds slightly faster by caching the results of PyArrow's C++ compilation steps.

Component(s)

Continuous Integration, Python

Activity

  1. pitrou commented on Aug 25, 2026

    @pitrou
    MemberAuthor
  2. changed the title [-][Python] CMakeLists detects ccache but not sccache[/-] [+][CI][Python] CMakeLists detects ccache but not sccache[/+] on Aug 25, 2026
  3. paultiq commented on Aug 25, 2026

    @paultiq
    Contributor

    While working on the 3.15 PR, I did this on a fork [and tested against my forked crossbow]:

    It got manylinux builds down to about 11-14 minutes, and started on Windows but didn't test.

    Steps for manylinux were:

    • Add an install step (in the dockerfile)
    • Disable ccache if sccache is available ARROW_USE_CCACHE:=OFF
    • Update CMakelists.txt to detect
    • Add sccache --show-stats at end of build

    ** I'm happy to take this issue, if interested.

  4. pitrou commented on Aug 25, 2026

    @pitrou
    MemberAuthor

    If you're talking about the Arrow C++ build step, there's #50992

    This issue is for PyArrow proper.

  5. paultiq commented on Aug 25, 2026

    @paultiq
    Contributor

    I'm talking about pyarrow proper: the crossbow wheel builds

    Example build: https://github.com/paultiq/crossbow/actions/runs/32308725974

  6. pitrou commented on Aug 25, 2026

    @pitrou
    MemberAuthor

    I'm talking about pyarrow proper: the crossbow wheel builds

    I mean there's a Arrow C++ build step there, and then a PyArrow build step :)

  7. paultiq commented on Aug 25, 2026

    @paultiq
    Contributor

    Oh, hah, gotcha... right... I'll meet you in #50992 :)

  8. med9110 commented on Oct 12, 2026

    @med9110

    Hi @pitrou, I'd be interested in working on this issue if it's still available.

    I'd like to implement the detection while preserving the existing ccache fallback behavior, and validate it with the relevant build checks.

    Does that approach sound right, and would you be happy for me to take this on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions