Skip to content

[C++] Add subdirectories to Meson Configuration #45778

Open
17 of 20 issues completed
Open

Description

@WillAyd

Describe the enhancement requested

The following subdirectories need to be implemented in the Meson build system:

Component(s)

C++

Activity

  1. raulcd commented on May 5, 2025

    @raulcd
    Member

    I am trying to fix the meson build on my PR but I am struggling to build locally and I would like to be able to limit the local resources it uses. How can I limit the number of processors being used in the meson build?
    I've tried modifying the n_jobs on cpp_build.sh as I can do for CMake but it doesn't seem to affect the meson build.

  2. WillAyd commented on May 5, 2025

    @WillAyd
    ContributorAuthor

    The easiest way would be to pass the -j argument when calling meson compile

  3. raulcd commented on May 5, 2025

    @raulcd
    Member

    but we are not using meson compile on our cpp_build.sh script, right?
    I can see meson setup and meson install there:
    I am trying to use the same CI job we use locally via: ARCHERY_DEBUG=1 archery docker run -e ARROW_USE_MESON=ON conda-cpp.
    I can open a separate issue if you want.

  4. WillAyd commented on May 5, 2025

    @WillAyd
    ContributorAuthor

    Ah interesting. We can add a compile step before the install then if we need to use a non-default invocation of it

  5. WillAyd commented on May 5, 2025

    @WillAyd
    ContributorAuthor

    I'll open a dedicated issue and PR for that later. Thanks for trying this out @raulcd !

  6. github-actions commented on May 25, 2026

    @github-actions

    This issue has been marked as stale because it has had no activity in the past 365 days. Please remove the stale label or comment below, or this issue will be closed in 14 days. If this improvement is still desired but has no current owner, please add the 'Status: needs champion' label.

  7. added
    Status: stale-warningIssues and PRs flagged as stale which are due to be closed if no indication otherwise
    on May 25, 2026
  8. removed
    Status: stale-warningIssues and PRs flagged as stale which are due to be closed if no indication otherwise
    on May 26, 2026
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