Several build-portability fixes already have open PRs across submodules — a roundup
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- cmake, cpp
- Ambito
- build-system, devtools
Direzione di ricerca
This issue is a roundup across submodules, and most listed fixes already have open pull requests. Start by checking the linked PRs for status and overlap; the two unclaimed changes name scene_rdl2/lib/render/util/IndexableArray.h and arras/distributed/CMakeLists.txt. The work is done when maintainers choose which outstanding portability fixes to take forward and redundant proposals are resolved.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Context
While updating the Arch Linux openmoonray AUR package to v2026.29.1, I've been maintaining a local patch to build cleanly on a modern toolchain (GCC 16, Boost 1.92, TBB 2023+, CMake 4, and a monolithic USD package). Cross-checking that patch against open PRs across the org, most of it turns out to already be proposed upstream — just sitting unreviewed, some for months. Listing them here in case it's useful to have them in one place.
I also checked each of these against the Rocky 9 build (GCC ~11, Boost 1.75, classic TBB 2020.3, non-monolithic USD, per building/Rocky9/install_packages.sh): none of them regress that build. The version/include fixes are backward-compatible no-ops there, and the two USD/TBB CMake changes are guarded (if(TARGET usd_ms), find_package(TBB CONFIG) falling through when not found) so they simply don't trigger on that toolchain.
Ready to merge (single PR each, exact fix)
arras_render#2 — missing<functional>include inOrbitCam.hcmake_modules#2 — prefer modern system-provided TBB viafind_package(TBB CONFIG)before falling back to the bundled find-modulehdMoonray#5 — support monolithic USD builds (interface polyfills for a combinedusd_mstarget)moonray_sdr_plugins#1 — same monolithic-USD fixmoonshine_usd#1 — same monolithic-USD fixmoonray#12 — disable AVX512PF/AVX512ER cpuid checks removed from newer compiler headersmoonray_gui#3 — standardize onQ_EMIT/Q_SIGNALS/Q_SLOTSto avoid the Qt/TBB keyword collision (covers 7 files, supersedes older #1/#2)moonshine#8 —DwaBaseattribute lookup fix for stricter C++ standards
Same fix, multiple competing open PRs (worth picking one and closing the rest)
mcrt_dataio: #6, #7, #9 all add the same missing<cstdint>include inClockDelta.hscene_rdl2: #11 (narrow) and #13 (broader, also coversBinPacketDictionary.hand the python CMake Boost::system removal) overlap
Already merged
arras4_core#8 — Boostio_service→io_context, dropBoost::system🎉
No PR yet, if anyone wants to pick these up
scene_rdl2/lib/render/util/IndexableArray.h—typename hasher::result_type→std::size_t(the former isn't guaranteed bystd::hashin a way that compiles cleanly everywhere)- top-level
arras/distributed/CMakeLists.txt— dropsystemfrom its Boostfind_packageCOMPONENTS list (same class of fix as the merged arras4_core one)
Happy to help review/rebase any of the above if that's useful — just flagging since they'd remove a good chunk of what downstream packagers currently have to patch around.
- Lingua principale
- CMake
- Stelle
- 4.7k
- Fork
- 321
- Merge medio
- 13m
- PR unite (30g)
- 3
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di OpenMoonRay/openmoonray
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
OpenMoonRay/openmoonray#332 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
OpenMoonRay/openmoonray#320 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
OpenMoonRay/openmoonray#233 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 57/100
OpenMoonRay/openmoonray#331 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
OpenMoonRay/openmoonray#330 ·
Tutte le issue di OpenMoonRay/openmoonray
Issue simili
-
priority: low tests
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
TMHSDigital/Free-Game-Dev-Assets#265 ·
I maintainer di solito rispondono entro 1 giorno
-
package-update
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
oSoWoSo/oco#889 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
cleanup documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 2 giorni
-
Specify Dependency VersionsApertabackend Setup
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
MatthewJ121/NutriGator#64 ·
I maintainer di solito rispondono entro 1 giorno
-
check-typing: ty 0.0.98+ fails on the renamed rule `unresolved-import` (now `import-not-found`)Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
crossbario/crossbar#2383 ·
I maintainer di solito rispondono entro 1 giorno