You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[C++] Add subdirectories to Meson Configuration #45778
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.
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.
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.
Activity
raulcd commentedon May 5, 2025
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_jobsoncpp_build.shas I can do for CMake but it doesn't seem to affect the meson build.WillAyd commentedon May 5, 2025
The easiest way would be to pass the -j argument when calling meson compile
raulcd commentedon May 5, 2025
but we are not using
meson compileon ourcpp_build.shscript, 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.
WillAyd commentedon May 5, 2025
Ah interesting. We can add a compile step before the install then if we need to use a non-default invocation of it
WillAyd commentedon May 5, 2025
I'll open a dedicated issue and PR for that later. Thanks for trying this out @raulcd !
github-actions commentedon May 25, 2026
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.