Posts

Post marked as solved
1 Replies
I could figure: The PRO-File has to contain: QMAKEMACOSXDEPLOYMENT_TARGET=10.13
Post not yet marked as solved
6 Replies
Also thanks a lot to you. I will investigate asap and get back.
Post not yet marked as solved
6 Replies
Got it - this helped me to better unstand the signing procedure ! This is turn leads to the next question:The deployment as a DMG-File is realized via the macdeployqt call.Do I understand correctly that I have to sign the final reployed DMG file ?Alternatively I could apply macdeployqt without creating a DMG file, then sign the result and then create a DMG of it.What makes most sense ?Thanks,bestAlex
Post not yet marked as solved
6 Replies
>>Please don't use "--deep" and "--force" to sign anything.I did it also without but it didn't make a difference.>>Are you embedding your framework inside your app? I am signing the app directly after the build. Deployment is realized afterwards but I haven't done it because the app crashes after the signature already (it does not without).>>And signing it properly?Yes, see above - it is also verified.>>What happens when you test it in a VM that isn't your development machine with Qt already installed?See above - it crashes already on my own machine before deployment.BestAlex