Re: [Interest] codesign issue with Qt6.9.1

Thu, 18 Sep 2025 11:50:29 -0700

Hello Kai,
 
>>Any reason you don’t use macdeployqt -codesign=“My dev account” ? This should do deep signing...
 
when I do this and I check the result via 
 
codesign --verify --deep --strict --verbose=2 ./myApp.app
 
it looks fine:
 
./myApp.app: valid on disk
./myApp.app: satisfies its Designated Requirement
 
 but indeed I need to include the entitlements:
 
--entitlements ./deployment/entitlements.xml
 
which seems to not work when combining it via macdeployqt or am I mistaken on this ?
 
Any further help appeciated,
thanks beforehand and
best
 
Alex
 
--
http://www.carot.de
Email : [email protected]
Tel.: +49 (0)177 5719797
 
Gesendet: Donnerstag, 18. September 2025 um 17:44
Von: "Kai Köhne via Interest" <[email protected]>
Betreff: Re: [Interest] codesign issue with Qt6.9.1

Confidential

>On 17/09/2025 8:31 pm, Alexander Carôt via Interest wrote:
>> Hello all,
>>
>> I just upgraded from Qt6.5.3 to Qt 6.9.1 – it's all fine except that now the codesigning fails. I typically do:
>>
>> macdeployqt My.app
>>
>> codesign --options=runtime --entitlements ./deployment/entitlements.xml --deep ./My.app -s "My dev account"
>
> According to the manual, --deep is deprecated - probably because it’s
> unreliable. You're expected to recurse all of the frameworks yourself, I
> think.
 
Any reason you don’t use macdeployqt -codesign=“My dev account” ? This should do deep signing...
 
>I don't know why codesign is so bad. But also I'm surprised that Qt is
> still shipping the official binaries unsigned.

Huh, they are signed?

Regards
 
Kai
_______________________________________________ Interest mailing list [email protected] https://lists.qt-project.org/listinfo/interest
_______________________________________________
Interest mailing list
[email protected]
https://lists.qt-project.org/listinfo/interest

Reply via email to