Cool VL Viewer forum

I attempted to build Cool VL Viewer v1.32.2.5 this afternoon. The build appeared to run correctly but when I copied the application to the Applications folder of my "recreation" Mac and attempted to run it, it immediately crashed on startup (log attached below). The application is looking for a dynamic library (libopenal.dylib) and not finding it.

So I went to my build machine and attempted to run Cool VL Viewer v1.32.2.5 on that, and it started up and ran, but only after it had asked me to allow the app to access the build directory tree, presumably to access the dynamic library above.

I used my normal build process which worked fine up to v1.32.2.3. I did not build v1.32.2.4 because I have a small enough Inventory to have avoided the problem that release addressed. Has something changed, or have I screwed up the build somehow?

You can disable OpenAL for building line 137 of indra/cmake/00-BuildOptions.cmake (change it for set(OPENAL OFF)), and the viewer will run using only FMOD like it did previously on macOS.

However, the libopenal.dylib should be properly copied into the app resources directory together with the other libraries (see scripts/viewer_manifest.py) , so macOS should find it...

Someone more knowledgeable than me about macOS would have to look at this (maybe a rpath to set for that library ?... Dunno).

In the mean time, I will disable again OpenAL support for macOS in next release...

This feels related to the draconian security that MacOS has implemented. I have also been building the Mac version for a while now, with no issues. I checked the .5 build (that I had crafted over the weekend but never run) and I got a similar behavior. All the expected libs are present in the Resources folder yet launching via my 'keyboard accelerator' failed. The accelerator has full disk access. I decided to invoke via Terminal using the 'open' command and it started right up with no errors. The Terminal app also has full disk access. After shutting down the command line initiated instance, I could then use my 'keyboard accelerator' app to launch without error. I'm wondering if some sort of application 'signature/hash' changed and MacOS decided that might be a security violation.

That's a very valuable feedback, thank you !

Maybe the OpenAL library has been signed differently by LL... Dunno.

It just occurred to me that I also did spurious reboot in the middle of my testing. That could have contributed to 'it works for me now'. I wasn't as diligent with my testing, unfortunately. It does feel like the OS decided for whatever reason, even if temporarily, to block access to some of the files. I have half a suspicion if we turned off OpenAL during the build, then perhaps another lib would have caused a similar issue. Just my speculations though. I don't develop on a Mac very much.

On checking, I find the "missing" library is in the Resources folder of the app I built, so the why the viewer is claiming it is missing I do not know. I will try the workaround Henri suggests above.

Cool VL Viewer v1.32.2.6 built and ran just fine.

Well, not really a surprise, since I just reverted the build option to no OpenAL support for macOS...

Yet, if someone knowledgeable with macOS stuff could have a look into this, I'd be grateful to them...

I wish I were more knowledgeable on this item. I can use OpenAL though when I build (I turned it back on in 00-BuildOptions.cmake, and disabled FMOD). Since I managed to get Cool VL Viewer to load once, after getting the same initial behaviour as linyifei, it's worked every time. Maybe Catten will have more insights when they build.