# Why aren't we building the extensions in parallel?

**URL:** <https://discourse.slicer.org/t/why-arent-we-building-the-extensions-in-parallel/47155>\
**Category:** Support\
**Created:** [May 27, 2026, 6:10pm UTC](https://discourse.slicer.org/t/why-arent-we-building-the-extensions-in-parallel/47155 "2026-05-27T18:10:21Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [May 27, 2026, 11:48pm UTC](https://discourse.slicer.org/t/why-arent-we-building-the-extensions-in-parallel/47155/9 "2026-05-27T23:48:01Z")

</div>

Per most recent Slicer hangout meeting notes, the next stable 5.12 will still require Rosetta for Apple Silicon Macs. There are likely additional build dependencies and build updates to make native arm builds possible. An Apple Silicon Mac will also need to be identified that will do the Slicer factory building, packaging and testing. Of course part of this work is making sure various parts extensions (primarily the compiled ones) are also still working on arm architecture. There are arm systems running Windows, Linux and macOS so it could be for all platforms.

> [@2026.05.26 Weekly Meeting](https://discourse.slicer.org/t/2026-05-26-weekly-meeting/47103/4):
>
> Meeting notes: Slicer 5.12 (Everyone) Slicer 5.12 release issue now exists: [Release Slicer v5.12 · Issue #9180 · Slicer/Slicer · GitHub](https://github.com/Slicer/Slicer/issues/9180) It is a good time to release 5.12 soon because we have a fairly clean dashboard and we are about tackle two problems that will create a broken nightly for a while: transtion to Qt6 and support mac arm64. Imported symbols in python console (Steve, Ebrahim) We should restore the legacy behavior in terms of things in slicer.util that were previously automaticall…

---

_[View the full topic](https://discourse.slicer.org/t/why-arent-we-building-the-extensions-in-parallel/47155)._