Yeah, that stack trace doesn’t mention exiv2 at all unlike the earlier ones.
Qt 5.12 is coming out later this month? I should probably test the beta…
edit: unlike 5.11 which required some changes, 5.12 seems to work just fine.
Yeah, that stack trace doesn’t mention exiv2 at all unlike the earlier ones.
Qt 5.12 is coming out later this month? I should probably test the beta…
edit: unlike 5.11 which required some changes, 5.12 seems to work just fine.
Here is a build with qt5.12.0b4
https://filebin.net/8fvnlsbl8tjuhqxt/Filmulator_1.0.0b4.zip?t=60u1hhyb
Out of the box Qt 5.12.0b4 comes compiled for 10.12 using the 10.14 sdk.
So this build is limited to macOS ≥ 10.12
It looks like qt5.12 depends on NSNotificationName which only shows up in macOS version 10.12 and higher.
It seems that this new version didn’t change anything.
The stack trace is the same save for a few of the offsets.
@CarVac or @chroma_ghost could you get the output in Mojave for
QT_DEBUG_PLUGINS=1 /Applications/Filmulator.app/Contents/MacOS/filmulator-gui
Thanks
Seems to load Qt okay. Did it crash with an error?
There are four b_versions of filmulator right now, I got a bit confused, thought b4 was for 10.12 only… If I’m not mistaken the above output is for b3. Sorry about that, for extra clarity “try this on X version” (?) will help me brain
Anyway here’s the output for a clean install of FL_b4 in Mojave. Imported folder with raws, filmulated (oh yeah, sounds dirty… like in the chemical days) one of them, exported tif & jpg. Seemed OK
QT_DEBUG_filmu_b4.txt.zip (9.2 KB)
Thanks for testing @chroma_ghost !
Do you use dark mode in mojave?
Due to the advanced Qt 5.12 version (a major component of the Filmulator bundle), the b4 version will not run on OS X before 10.12, and what we were wondering with this round is whether the app runs and filmulates on 10.14 Mojave.
Do you use dark mode in mojave?
of course I do, I don’t even try to resist it
In the end we never figured out what was wrong, and Filmulator started working for them.
???
I’m profoundly unsatisfied with how that turned out, but it’s working now…
Yeah that was weird, but we were not able to reproduce. I now have a Mojave system to test on. Seems working ok.
Btw filmulator build w/Qt 5.9 is working ok on Macos Mojave 10.14.2beta18C48a.
https://kd6kxr.keybase.pub/filmulator_v0.7.0-62-g19f4039.dmg
https://kd6kxr.keybase.pub/Filmulator-v0.7.0-100-gaa026d0.dmg
Thanks to @asn Filmulator can now be built with cmake as well as qmake, so hopefully that makes it easier to build for mac.
Now they should be there, inside the inner filmulator-gui directory.
@carvac @asn Ok, this works great generating the binary. I used this method.
$ export QT=~/Qt511/5.11.1/clang_64
$ cmake -DCMAKE_BUILD_TYPE="release" -DCMAKE_CXX_COMPILER="clang++" -DCMAKE_CXX_FLAGS=-I/opt/local/include -DCMAKE_OSX_SYSROOT="/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk" -DCMAKE_OSX_DEPLOYMENT_TARGET="10.9" -DOpenMP_CXX_FLAGS="-Xpreprocessor -fopenmp /opt/local/lib/libomp.dylib -I/opt/local/include"-DOpenMP_CXX_LIB_NAMES="libomp" -DOpenMP_libomp_LIBRARY=/opt/local/lib/libomp.dylib -DCMAKE_INSTALL_PREFIX=/opt/local -DCMAKE_SHARED_LINKER_FLAGS=-L/opt/local/lib -DCMAKE_PREFIX_PATH=$(echo $QT/lib/cmake/* | sed -Ee 's$ $;$g') -G "Unix Makefiles" ..
$ make -j$(sysctl -n hw.ncpu)
Deploying to a fresh app bundle would be a good next phase for mac.
Could you add that to the build instructions in the README?