Software, LLC
[e] mike.jack...@bluequartz.net
[w] www.bluequartz.net
From: Interest on behalf of Alexander Carôt
Date: Wednesday, April 8, 2020 at 12:29 PM
To: Andy
Cc: qt qt
Subject: Re: [Interest] OSX codesign question
Hej Nuno and Andy,
thanks a lot - yes, it is confusing but
.@carot.de
> Tel.: +49 (0)177 5719797
>
>
> *Gesendet:* Donnerstag, 09. April 2020 um 02:40 Uhr
> *Von:* "Hamish Moffatt"
> *An:* interest@qt-project.org
> *Betreff:* Re: [Interest] OSX codesign question
> On 9/4/20 1:15 am, "Alexander Carôt" wrote:
>
> So
"
An: interest@qt-project.org
Betreff: Re: [Interest] OSX codesign question
On 9/4/20 1:15 am, "Alexander Carôt" wrote:
So - I received the new certificate, installed it on my keychain tool and this is what happened again:
soulalex@alexandarotsMBP SJC % codesign --deep --forc
On 9/4/20 1:15 am, "Alexander Carôt" wrote:
So - I received the new certificate, installed it on my keychain tool
and this is what happened again:
soulalex@alexandarotsMBP SJC % codesign --deep --force --verify
--verbose --timestamp --options runtime --sign "Developer ID
Application: Alexander
Von: Andy <asmalo...@gmail.com>
Datum: Montag, 6. April 2020 um 13:34
An: Nuno Santos <nunosan...@imaginando.pt>
Cc: Alexander Carôt <alexander_ca...@gmx.net>, qt qt <interest@qt-project.org>
Betreff: Re: [Interest] OSX codesign question
I just did this yes
>
> Tel.: +49 (0)177 5719797
>
>
>
>
>
> *Von: *Andy
> *Datum: *Montag, 6. April 2020 um 13:34
> *An: *Nuno Santos
> *Cc: *Alexander Carôt , qt qt <
> interest@qt-project.org>
> *Betreff: *Re: [Interest] OSX codesign question
>
>
>
> I j
; Datum: Montag, 6. April 2020 um 13:34
> An: Nuno Santos mailto:nunosan...@imaginando.pt>>
> Cc: Alexander Carôt <mailto:alexander_ca...@gmx.net>>, qt qt <mailto:interest@qt-project.org>>
> Betreff: Re: [Interest] OSX codesign question
>
> I just did this yesterday.
: Andy
Datum: Montag, 6. April 2020 um 13:34
An: Nuno Santos
Cc: Alexander Carôt , qt qt
Betreff: Re: [Interest] OSX codesign question
I just did this yesterday. I could not get macdeployqt to work either, so I do
it using the command line in my build process.
Here's the command lin
I just did this yesterday. I could not get macdeployqt to work either, so I
do it using the command line in my build process.
Here's the command line I'm using:
codesign --deep --force --verify --verbose --timestamp --options runtime
--sign "${CODE_SIGNING_ID}" "${APP_PATH}"
Which signing ID y
Alexander,
I don’t use macdeployqt for signing.
I call the codesign command manually in the POST LINK phase.
You need to pass to the code sign the string representing your team. You can
list the available signing entities with the following command:
> security find-identity -v -p codesigning
ôt"
Cc: "qt qt"
Betreff: Re: [Interest] OSX codesign question
You might be missing some magical commands to import the identity - check out https://github.com/Mudlet/Mudlet/blob/development/CI/travis.osx.after_success.sh#L17 for an example.
___
You might be missing some magical commands to import the identity - check
out
https://github.com/Mudlet/Mudlet/blob/development/CI/travis.osx.after_success.sh#L17
for an example.
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.o
Hello all,
I want to sign my OSX code in order to have it running on a client's machine
without the need to right-click and open it.
I signed at https://developer.apple.com/ and received my valid certificate
called "developer.cer".
Then I exectued
macdeployqt myApp.app -dmg -codesign=develope
13 matches
Mail list logo
