# Nightly mac Slicer-4.9.0-2018-03-13-macosx-amd64 does not open

**URL:** <https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313>\
**Category:** Development\
**Created:** [March 14, 2018, 1:23pm UTC](https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313 "2018-03-14T13:23:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [March 14, 2018, 1:23pm UTC](https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313/1 "2018-03-14T13:23:13Z")

</div>

Message is:

```auto

Termination Reason: DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @rpath/Frameworks/QtMultimedia.framework/Versions/5/QtMultimedia
  Referenced from: /private/var/folders/*/Slicer.app/Contents/MacOS/Slicer
  Reason: image not found

```

All the Slicer.app/Contents/Frameworks/Qt\*.framework/Versions/5 directories are empty, whereas in previous builds they include the libraries.

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [March 14, 2018, 1:53pm UTC](https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313/2 "2018-03-14T13:53:59Z")

</div>

~~I wasn’t able to open that package at all from Finder – nothing happened after double-clicking.~~ I was able to load the image successfully with `hdiutil attach <Slicer-###.dmg>`, and the Qt frameworks seem to be there (Slicer starts ok).

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [March 14, 2018, 7:27pm UTC](https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313/3 "2018-03-14T19:27:23Z")

</div>

@ihnorton Can you check which version the dmg you are using? There are two with the same name/data in midas:

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/0/a/0aee37e9df39cc29de74088270a86ebc27b49df4.png)

The one with the (1) postfix is the one with the missing frameworks while the other one (from yesterday) does have the frameworks.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/d/d/dd90f9fb545ee0f71c2b14bf86dcb9a426dd01c0.png)

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [March 14, 2018, 7:29pm UTC](https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313/4 "2018-03-14T19:29:03Z")

</div>

The one I have is reported as 295 MB on-disk, so must be the first one.

edit: not sure what happened last time I tried, but just double-clicked the .dmg again, and the `open` dialog popped right up.

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [March 14, 2018, 7:30pm UTC](https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313/5 "2018-03-14T19:30:56Z")

</div>

@jcfr Maybe one of the changes to the dashboard scripts yesterday changed the packaging of Qt frameworks…

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [March 15, 2018, 2:35am UTC](https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313/6 "2018-03-15T02:35:23Z")

</div>

> [@pieper](#):
>
> Maybe one of the changes to the dashboard scripts yesterday changed the packaging of Qt frameworks…

Good point.

**Prior** to the update of the scripts, a custom build of Qt 5.10.0 was used (with complete run time paths). See [here](https://github.com/Slicer/DashboardScripts/blob/a4b631f3e9b819dbc47acf8a4794cb33b62b8cf0/factory-south-macos-slicer_release_nightly.cmake#L29). **After** , a regular install of 5.9.1 was used. See [here](https://github.com/Slicer/DashboardScripts/blob/5ab84211a80ff3d51eadfd3965cfb068688d54be/factory-south-macos-slicer_preview_nightly.cmake#L32-L33) (with fixed references to library using `@rpath`).

This was an oversight that is now **fixed** in [Slicer/DashboardScripts@877c0ce](https://github.com/Slicer/DashboardScripts/commit/877c0ceb7796b33bbfad67b51f469ee21391cae5)

Until the improvements of @ihnorton ([Slicer PR#889](https://github.com/Slicer/Slicer/pull/889)) are finalized and integrated, on macOS we need to package Slicer using a custom build of Slicer.

In the mean time, anyone can build Qt 5.10.0 on macOS using [GitHub - jcfr/qt-easy-build: Scripts allowing to easily build Qt with OpenSSL support on Linux, macOS or Windows](https://github.com/jcfr/qt-easy-build)

![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/3/e/3e513557841149468f575832806a1adfd2f22964.png)

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [March 15, 2018, 8:25am UTC](https://discourse.slicer.org/t/nightly-mac-slicer-4-9-0-2018-03-13-macosx-amd64-does-not-open/2313/7 "2018-03-15T08:25:44Z")

</div>

2 posts were split to a new topic: [macOS build on the factory failed with “No Java runtime present … Alarm clock: 14”](https://discourse.slicer.org/t/macos-build-on-the-factory-failed-with-no-java-runtime-present-alarm-clock-14/2321)