1 Topic by scorpio810 (edited by scorpio810 2023-01-20 10:11:18)

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Topic: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Until now QElectroTech team bundles were made under linux with OSX KVM for X86_64 Intel macOS. Obviously it takes a lot of work, knowledge, time consuming to make it.

I would like to buy the new mac mini M2 to make universal bundles for macOS (arch:amd64 & arm64), for that we are missing about 300€ on our Paypal to buy a 699€ the MAC Mini M2, are you ready to help us in this adventure?
https://www.apple.com/fr/shop/buy-mac/m … 3urs-256go

https://qelectrotech.org/forum/viewtopi … 377#p17377

I slightly improved my AMD Threadripper OSX/KVM and gained a lot of fluidity without going through the GPU passthrough...
Compiling QET on Monterey take ~34 s with CLANG 14 vs 32 s with GCC on my Linux host, is fine, but emulating an APPLE Silicon amr64 in QEMU is a hassle... and you lost 80 % off Host CPU for emulate it!, otherwise you have Rosetta2 which should work fine I think, without too much slowdown, if you have any feedback?
I'll leave that aside for a moment.

BTW,

For those who already have an M1 or M2 APPLE silicon, if you can test the build environment here:
it's need  ~ 11 Go free on your disk and can take some many hours for building the build environment by arch.
https://qelectrotech.org/wiki_new/doc/m … t_new_2023

Or tell us how QET behaves with rosetta2 on an M1, M2..
Without a real MAC it is more difficult to improve the software under this OS...

Laurent

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

                100%
0[=====================] 700 €

They used the Donate button:
Thanks:

Mauro (IT)
Marco (CH)
Bernd (DE)
Jean (FR)
Anastasios  (EL)
Krystian (PL)
Philipp (DE)
Jean Pierre (BE)
Jacobo (ES)
Fabrice (FR)
Immanuel (DE)
Marcel (DE)
Miguel (PER)
Johannes (DE)
Marcel (DE)
Antonio (ES)
Ruben (DE)
Andre (DE)

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Can't build QET with MacPorts and Digikam scripts, I have linking errors:
............building for macOS-arm64 but attempting to link with file config macOS-x86_64..... For KF5 libs...

Ok! with Homebrew: ps: compile QET on mini M2 8Go 256Go take 60 s.

The time of compilation is 1 min 2 sec

12:35:04.709 Info: Elements collection finished to be loaded in 0.651 seconds 

:33:55.114 Info: Start-up 
12:33:55.122 Info: debugging enabled: false 
12:33:55.122 Info: Qt library version: 5.15.8 
12:33:55.122 Info: Qt library location default prefix: "/opt/homebrew/Cellar/qt@5/5.15.8_1" 
12:33:55.122 Info: Qt library location documentation: "/opt/homebrew/Cellar/qt@5/5.15.8_1/doc" 
12:33:55.122 Info: Qt library location headers: "/opt/homebrew/Cellar/qt@5/5.15.8_1/include" 
12:33:55.123 Info: Qt library location libraries: "/opt/homebrew/Cellar/qt@5/5.15.8_1/lib" 
12:33:55.123 Info: Qt library location executables: "/opt/homebrew/Cellar/qt@5/5.15.8_1/libexec" 
12:33:55.123 Info: Qt library location Qt binaries: "/opt/homebrew/Cellar/qt@5/5.15.8_1/bin" 
12:33:55.123 Info: Qt library location Qt plugins: "/opt/homebrew/Cellar/qt@5/5.15.8_1/plugins" 
12:33:55.123 Info: Qt library location installed QML extensions: "/opt/homebrew/Cellar/qt@5/5.15.8_1/imports" 
12:33:55.123 Info: Qt library location installed QML extensions: "/opt/homebrew/Cellar/qt@5/5.15.8_1/qml" 
12:33:55.123 Info: Qt library location dependent Qt data: "/opt/homebrew/Cellar/qt@5/5.15.8_1" 
12:33:55.123 Info: Qt library location independent Qt data: "/opt/homebrew/Cellar/qt@5/5.15.8_1" 
12:33:55.123 Info: Qt library location translation: "/opt/homebrew/Cellar/qt@5/5.15.8_1/translations" 
12:33:55.123 Info: Qt library location examples: "/opt/homebrew/Cellar/qt@5/5.15.8_1/examples" 
12:33:55.123 Info: Qt library location Qt testcases: "/opt/homebrew/Cellar/qt@5/5.15.8_1/tests" 
12:33:55.123 Info: Qt library location Qt settings: "/Library/Preferences/Qt" 
12:33:55.123 Info: "GitRevision 6e60842d6980f9d393bf234ccc4bc4963c62f720" 
12:33:55.123 Info: "QElectroTech V 0.100.0-dev" 
12:33:55.123 Info: "Compilation : CLANG 14.0.0 (clang-1400.0.29.202)" 
12:33:55.123 Info: "Built with Qt 5.15.8 - arm64 - Date : Feb  6 2023 : 12:13:31" 
12:33:55.123 Info: "Run with Qt 5.15.8 using 8 thread(s)" 
12:33:55.123 Info: "CPU : Apple M2\n" 
12:33:55.123 Info: "RAM Total : 8 GB" 
12:33:55.123 Info: "" 
12:33:55.123 Info: "GPU : " 
12:33:55.123 Info: "GPU RAM : " 
12:33:55.123 Info: "OS : darwin  - arm64 - Version : macOS 13.2 - Kernel : 22.3.0" 
12:33:55.123 Info: *** Qt screens *** 
12:33:55.123 Info: "( 1 : 3840 x 2160 )" 
12:33:55.152 Debug: isReadOnly: true (../sources/machine_info.cpp:161, void MachineInfo::send_info_to_debug())
12:33:55.152 Info: DISK : /   
12:33:55.153 Info: FileSystemType: "apfs" 
12:33:55.153 Info: SizeTotal: 245 GB 
12:33:55.153 Info: AvailableSize: 181 GB 
12:33:55.153 Debug: isReadOnly: true (../sources/machine_info.cpp:161, void MachineInfo::send_info_to_debug())
12:33:55.153 Info: DISK : /Volumes/qelectrotech   
12:33:55.153 Info: FileSystemType: "apfs" 
12:33:55.153 Info: SizeTotal: 0 GB 
12:33:55.153 Info: AvailableSize: 0 GB 
12:33:55.153 Debug: isReadOnly: true (../sources/machine_info.cpp:172, void MachineInfo::send_info_to_debug())
12:33:55.153 Info: DISK USED: /   
12:33:55.153 Info: FileSystemType: "apfs" 
12:33:55.153 Info: SizeTotal: 245 GB 
12:33:55.153 Info: AvailableSize: 181 GB 
12:33:55.310 Info: Elements collection reload 
12:33:55.321 Info: Elements collection finished to be loaded in 0.011 seconds 
12:35:03.838 Info: Start-up 
12:35:03.845 Info: debugging enabled: false 
12:35:03.845 Info: Qt library version: 5.15.8 
12:35:03.846 Info: Qt library location default prefix: "/opt/homebrew/Cellar/qt@5/5.15.8_1" 
12:35:03.846 Info: Qt library location documentation: "/opt/homebrew/Cellar/qt@5/5.15.8_1/doc" 
12:35:03.846 Info: Qt library location headers: "/opt/homebrew/Cellar/qt@5/5.15.8_1/include" 
12:35:03.846 Info: Qt library location libraries: "/opt/homebrew/Cellar/qt@5/5.15.8_1/lib" 
12:35:03.846 Info: Qt library location executables: "/opt/homebrew/Cellar/qt@5/5.15.8_1/libexec" 
12:35:03.846 Info: Qt library location Qt binaries: "/opt/homebrew/Cellar/qt@5/5.15.8_1/bin" 
12:35:03.846 Info: Qt library location Qt plugins: "/opt/homebrew/Cellar/qt@5/5.15.8_1/plugins" 
12:35:03.846 Info: Qt library location installed QML extensions: "/opt/homebrew/Cellar/qt@5/5.15.8_1/imports" 
12:35:03.846 Info: Qt library location installed QML extensions: "/opt/homebrew/Cellar/qt@5/5.15.8_1/qml" 
12:35:03.846 Info: Qt library location dependent Qt data: "/opt/homebrew/Cellar/qt@5/5.15.8_1" 
12:35:03.846 Info: Qt library location independent Qt data: "/opt/homebrew/Cellar/qt@5/5.15.8_1" 
12:35:03.846 Info: Qt library location translation: "/opt/homebrew/Cellar/qt@5/5.15.8_1/translations" 
12:35:03.846 Info: Qt library location examples: "/opt/homebrew/Cellar/qt@5/5.15.8_1/examples" 
12:35:03.846 Info: Qt library location Qt testcases: "/opt/homebrew/Cellar/qt@5/5.15.8_1/tests" 
12:35:03.846 Info: Qt library location Qt settings: "/Library/Preferences/Qt" 
12:35:03.846 Info: "GitRevision 6e60842d6980f9d393bf234ccc4bc4963c62f720" 
12:35:03.846 Info: "QElectroTech V 0.100.0-dev" 
12:35:03.846 Info: "Compilation : CLANG 14.0.0 (clang-1400.0.29.202)" 
12:35:03.846 Info: "Built with Qt 5.15.8 - arm64 - Date : Feb  6 2023 : 12:13:31" 
12:35:03.846 Info: "Run with Qt 5.15.8 using 8 thread(s)" 
12:35:03.846 Info: "CPU : Apple M2\n" 
12:35:03.846 Info: "RAM Total : 8 GB" 
12:35:03.846 Info: "" 
12:35:03.846 Info: "GPU : " 
12:35:03.846 Info: "GPU RAM : " 
12:35:03.846 Info: "OS : darwin  - arm64 - Version : macOS 13.2 - Kernel : 22.3.0" 
12:35:03.847 Info: *** Qt screens *** 
12:35:03.847 Info: "( 1 : 3840 x 2160 )" 
12:35:03.847 Debug: isReadOnly: true (../sources/machine_info.cpp:161, void MachineInfo::send_info_to_debug())
12:35:03.847 Info: DISK : /   
12:35:03.847 Info: FileSystemType: "apfs" 
12:35:03.847 Info: SizeTotal: 245 GB 
12:35:03.847 Info: AvailableSize: 181 GB 
12:35:03.847 Debug: isReadOnly: true (../sources/machine_info.cpp:161, void MachineInfo::send_info_to_debug())
12:35:03.847 Info: DISK : /Volumes/qelectrotech   
12:35:03.847 Info: FileSystemType: "apfs" 
12:35:03.847 Info: SizeTotal: 0 GB 
12:35:03.847 Info: AvailableSize: 0 GB 
12:35:03.847 Debug: isReadOnly: true (../sources/machine_info.cpp:172, void MachineInfo::send_info_to_debug())
12:35:03.847 Info: DISK USED: /   
12:35:03.847 Info: FileSystemType: "apfs" 
12:35:03.847 Info: SizeTotal: 245 GB 
12:35:03.847 Info: AvailableSize: 181 GB 
12:35:04.056 Info: Elements collection reload 
12:35:04.709 Info: Elements collection finished to be loaded in 0.651 seconds

https://download.tuxfamily.org/qet/forum_img_2/Capture%20d%e2%80%99%c3%a9cran%202023-02-06%20%c3%a0%2012.37.32.png

https://download.tuxfamily.org/qet/forum_img_2/Capture%20d%e2%80%99%c3%a9cran%202023-02-06%20%c3%a0%2012.48.52.png

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Compile and program works well, but if I use macdeployqt to make packaging bundle, bundle crash on launch time.
Long is the road .....


-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               qelectrotech [14278]
Path:                  /Applications/qelectrotech.app/Contents/MacOS/qelectrotech
Identifier:            org.qelectrotech
Version:               0.100.0 r7821 (???)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2023-02-06 12:58:50.0242 +0100
OS Version:            macOS 13.2 (22D49)
Report Version:        12
Anonymous UUID:        

Sleep/Wake UUID:       
Time Awake Since Boot: 6700 seconds
Time Since Wake:       3610 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Exception Codes:       UNKNOWN_0x32 at 0x00000001033f4000
Exception Codes:       0x0000000000000032, 0x00000001033f4000

Termination Reason:    Namespace CODESIGNING, Code 2 Invalid Page

EDIT: Ok some more progress here:
https://kubadownload.com/news/codesign-sign-app/

Todo:
https://eclecticlight.co/2019/01/17/cod … ng-an-app/
https://stackoverflow.com/questions/238 … ile-in-mac
https://stackoverflow.com/questions/426 … er-for-osx
https://wiki.freepascal.org/Notarizatio … 10.14.5%2B

https://github.com/crystalidea/macdeployqt-universal

Ok with:

codesign --force --deep --sign - /Applications/qelectrotech.app

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

On Apple Silicon M1/M2 try new bundle arm64 packages:

Need after for now:

codesign --force --deep --sign - /Applications/qelectrotech.app

BTW, sqlite3 export of project database didn't work yet with my new Brew arm64 (Apple silicon) packages, so if you want it use Intel X86_64 bundle dmg.

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Please try qelectrotech.app
https://download.tuxfamily.org/qet/scor … ch.app.zip

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

A native M1 packaging need a signed Apple developer account. You need to pay 100 euros for that by year, which is unacceptable for an open source project. This is not yet the case for x86 packaging.

https://discuss.pixls.us/t/digikam-7-5- … ed/28921/3

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

I did not study this problem today, but I confirm that QET under mac mini M2 and compiled natively works much better than the package emulated with Roseta 2 and also well under linux or Windows but:

1] You need disabling Gatekeeper

sudo spctl --master-disable

2 ] Then need again to install Xcode program and re-sign the package and its libraries otherwise it will crash on launch...

codesign --force --deep --sign - /Applications/qelectrotech.app

But a novice macOS user is not going to install the Xcode development program which is very heavy and which takes about ten Giga bytes to run QElectroTech, he wants to click on the bundle, do the editing and simply drag and drop qelectrotech. app to Applications to install it....



From what I understand Apple now obliges and forces to have an Apple developer key to sign the packages for their aplle silicon M1/M2 chips, otherwise it will not install on their imac, mac mini, mac sutdio M1 M2 which are arm64 architecture instead of X86_64 for intel or AMD cpus, on the other hand all this at a cost, and you still have to pay 100 €/year to obtain the key.

I have already spent more than 250 € out of my pocket to buy the cheapest mac mini M2 while waiting for the donations to arrive, having struggled with my PC keyboard and wasting time each time finding where the special keys were regularly used for scripts and code like "#&_-,$!%, etc" I reluctantly decided to pay out of my own pocket for an extended magic keybord keyboard for around 150 €, the paypal kitty is zero at this point. moment, and I have advanced too far on my money side to pay the aplle developer subscription to sign the packages, here is where we are today ...



Unfortunately, I can't afford to keep putting money out of my pocket...as I reach the goal of running QET on Linux as well as macOS M1/M2!

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Just a little video to show you that QET works very well on a native arm64 compilation on mac mini M2 8Go 256G:
Much better than intel X86_64 builds emulated by roseta2...


https://youtu.be/Gr90uxlt2nA

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

scorpio810 wrote:

Please try qelectrotech.app
https://download.tuxfamily.org/qet/scor … ch.app.zip

I tried qelectrotech.app on UTM macOS Ventura VM.
Just :
You need disabling Gatekeeper

sudo spctl --master-disable

Drag and drop qelectrotech.app in your Applications folder.


Enjoy! nomicons/wink


https://download.tuxfamily.org/qet/forum_img_2/utm_applem1.png


https://download.tuxfamily.org/qet/forum_img_2/utm_applem2.png
https://wiki.freepascal.org/Code_Signing_for_macOS
https://stackoverflow.com/questions/601 … -is-hidden

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

it was not possible for me to have a free developer account, despite my emails and phone calls with Apple support..
We are not a declared registration so impossible to have a DUNS number, or else I would have to become self-employed...

I was told that it was better to pay with your credit card than with a Paypal account to facilitate authentication..., so I had to pay again out of my pocket 99€/year...



After many hours, and days to learn I couldn't sign a dmg, although codesign -dv -r- /Applications/qelectrotech.app is ok, but QET crashes...on launch or does not launch...
So I modified my scripts to package a zip tarball..

Compile, sign, zip and upload:

The time of compilation is 1 min 5 sec

______________________________________________________________
Copy Qt libraries and private frameworks:
Processing Mac deployment tool...

______________________________________________________________
Copy file missing:
Copying add elements in the bundle...
Copying titleblocks in the bundle...
Copying translations in the bundle... 
Copying translations in the bundle... 
qelectrotech.app: replacing existing signature

______________________________________________________________
Create disk image:

______________________________________________________________
The process of creating deployable application zip is done.
The disque image is in the folder 'build-aux/mac-osx'.
Would you like to upload MacOS packages qelectrotech-0.100.0-r7840-arm64.zip, n/Y?.
y
xxxxxx@ssh.tuxfamily.org's password: 
building file list ... 
2 files to consider
./
qelectrotech-0.100.0-r7840-arm64.zip
    47283680 100%  692.58kB/s    0:01:06 (xfer#1, to-check=0/2)
deleting qelectrotech.app.zip

sent 47289601 bytes  received 48 bytes  587449.06 bytes/sec
total size is 47283680  speedup is 1.00


laurent@mini-de-laurent-1 ~ % codesign -dv -r- /Applications/qelectrotech.app
Executable=/Applications/qelectrotech.app/Contents/MacOS/qelectrotech
Identifier=org.qelectrotech
Format=app bundle with Mach-O thin (arm64)
CodeDirectory v=20400 size=64596 flags=0x0(none) hashes=2012+3 location=embedded
Signature size=8981
Timestamp=20 Mar 2023 at 11:58:52
Info.plist entries=14
TeamIdentifier=Y73WZ6WZ5X
Sealed Resources version=2 rules=13 files=9822
designated => identifier "org.qelectrotech" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] /* exists */ and certificate leaf[field.1.2.840.113635.100.6.1.13] /* exists */ and certificate leaf[subject.OU] = Y73WZ6WZ5X
laurent@mini-de-laurent-1 ~ %

Next step is learning notarize application for gatekeeper...
https://developer.apple.com/documentati … n_workflow
https://github.com/electron/notarize/issues/88
https://scriptingosx.com/2021/07/notari … otarytool/
https://melatonin.dev/blog/how-to-code- … ins-in-ci/
https://blog.smittytone.net/2022/06/09/ … e-quickly/
https://blog.rampatra.com/how-to-notari … otary-tool

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Check Notarizing macOS software before distribution:

https://developer.apple.com/documentati … stribution

Overview
Notarization gives users more confidence that the Developer ID-signed software you distribute has been checked by Apple for malicious components. Notarization is not App Review. The Apple notary service is an automated system that scans your software for malicious content, checks for code-signing issues, and returns the results to you quickly. If there are no issues, the notary service generates a ticket for you to staple to your software; the notary service also publishes that ticket online where Gatekeeper can find it.

When the user first installs or runs your software, the presence of a ticket (either online or attached to the executable) tells Gatekeeper that Apple notarized the software. Gatekeeper then places descriptive information in the initial launch dialog to help the user make an informed choice about whether to launch the app.

laurent@mini-de-laurent-1 ~ % cd MAC_OS_X                                                                                                                      
laurent@mini-de-laurent-1 MAC_OS_X % xcrun notarytool submit qelectrotech-0.100.0-r7842-arm64.zip --keychain-profile "org.qelectrotech" --wait 
Conducting pre-submission checks for qelectrotech-0.100.0-r7842-arm64.zip and initiating connection to the Apple notary service...
Submission ID received
  id: 7b03eca5-29c1-4948-b406-637fac2de3a0
Upload progress: 100,00 % (48,1 MB of 48,1 MB)   
Successfully uploaded file
  id: 7b03eca5-29c1-4948-b406-637fac2de3a0
  path: /Users/laurent/MAC_OS_X/qelectrotech-0.100.0-r7842-arm64.zip
Waiting for processing to complete.
Current status: Accepted..............................
Processing complete
  id: 7b03eca5-29c1-4948-b406-637fac2de3a0
  status: Accepted
laurent@mini-de-laurent-1 MAC_OS_X %

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

MacQetDeploy_arm64.sh add Enable hardened runtime flag to fix notarization fail,
Add process to Upload a macOS app to be notarized and validate before upload to QET download servers


The time of compilation is 1 min 3 sec

______________________________________________________________
Copy Qt libraries and private frameworks:
Processing Mac deployment tool...

______________________________________________________________
Copy file missing:
Copying add elements in the bundle...
Copying titleblocks in the bundle...
Copying translations in the bundle... 
Copying translations in the bundle... 
Copying examples in the bundle... 
qelectrotech.app: replacing existing signature

______________________________________________________________
Create zip tarball:

______________________________________________________________
Notarize zip tarball:
Conducting pre-submission checks for qelectrotech-0.100.0-r7842-arm64.zip and initiating connection to the Apple notary service...
Submission ID received
  id: e5d26b8f-5981-49b0-b584-cf1ad2ac9a2b
Upload progress: 100,00 % (48,1 MB of 48,1 MB)   
Successfully uploaded file
  id: e5d26b8f-5981-49b0-b584-cf1ad2ac9a2b
  path: /Users/laurent/qet_git/build-aux/mac-osx/qelectrotech-0.100.0-r7842-arm64.zip
Waiting for processing to complete.
Current status: Accepted...........................
Processing complete
  id: e5d26b8f-5981-49b0-b584-cf1ad2ac9a2b
  status: Accepted

______________________________________________________________
The process of creating deployable application zip is done.
The disque image is in the folder 'build-aux/mac-osx'.
Would you like to upload MacOS packages qelectrotech-0.100.0-r7842-arm64.zip, n/Y?.
y
xxxxxxx@ssh.tuxfamily.org's password: 
building file list ... 
2 files to consider
./
qelectrotech-0.100.0-r7842-arm64.zip
    50451911 100%  692.76kB/s    0:01:11 (xfer#1, to-check=0/2)
deleting qelectrotech-0.100.0-r7840-arm64.zip

sent 50458220 bytes  received 48 bytes  604290.63 bytes/sec
total size is 50451911  speedup is 1.00
laurent@mini-de-laurent-1 ~ %

  • Joshua
  • Joshua
  • QElectroTech Team Developer
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

C'est incroyable, apple fait tout sont possible pour faire chier les petits dev comme nous..... et en plus il faut payer.....

Développeur QElectroTech
  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

https://opentoolchain.org/hackathon/

@Joshua:

J'ai du refuser au vu de mon état de santé très fragile, il m’était impossible de me déplacer et se rendre au FOSDEM 2023 à Hambourg en Allemagne..
J'ai pensé à toi, mais je sais que la santé de ta compagne est préoccupante et que tu ne pouvais pas faire le déplacement..


https://youtu.be/SQMlEnvvCR8


https://forum.opentoolchain.org/t/visua … lchains/77

https://forum.opentoolchain.org/uploads/default/original/1X/4d72511df8c698466a22912d9467874f0736e078.png

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Joshua wrote:

C'est incroyable, apple fait tout sont possible pour faire chier les petits dev comme nous..... et en plus il faut payer.....

C'est compliqué et je vais essayer de t'expliquer, c'est même impératif pour les puces M1 M2:
https://scriptingosx.com/2021/07/notari … otarytool/


1 ) il te faut tout d'abord un compte développeur Apple (Apple Developer Account) plus un autre compte (Developer ID Application) pour t'authentifier avec lequel tu signes le contenu de l'application, avec cela tu es certain que le paquet provient bien de moi et moi seul, que le paquet n'a pas été infecté ou bricolé par un autre sur un serveur de download, un peu comme l  SHA256 qu'on utilise aussi avec les signatures sur paquets Linux.

2) La notarization est la suite et un autre ensemble de clé et oui il faut d'autres certificats... two-factor authentication (2FA) qui avec la commande xcrun notarytool submit permet d'envoyer ton paquet sur un serveur Apple afin de vérifier que le 2FA two-factor authentication est valide, que tes signatures correspondent, en même temps il va vérifier que ton paquet ne contient aucun virus et autres saletés.

Ça prend un peu de temps ... le temps de recevoir la validation, si ok mon script fait un rsync pour uploader mon paquet sur les serveurs de Tuxfamily.org ..

A partir de là un ticket est émis correspondant, il va s'ajouter dans la base de données que Gatekeeper va interroger pour valider ou pas le lancement du logiciel, il est aussi possible de joindre ce ticket dans le paquet du logiciel pour ceux qui n'ont pas de réseau.. Je verrais ça plus tard!

Voila en quelques mots comment ça fonctionne..


Pour l'instant cela ne concerne que les paquets macOS arm64.

Apres pour que QET soit disponible sur l'APPLE store est une autre paire de manches...

  • Joshua
  • Joshua
  • QElectroTech Team Developer
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Merci d'avoir pensé à moi pour le FOSDEM, mais effectivement je ne peut pas faire le déplacement pour les raisons que tu évoques…


Au sujet d’Apple, du coup tout ça c’est pour permettre à l’utilisateur de la pomme d’utiliser des logiciels vérifié et exempte de saloperie (pas comme Windows ou l’on peut installer n’importe quoi n’importe comment), mais si le logiciel n’est pas développé par une entreprise ou à minima une asso, c’est tout de suite plus compliqué.

Développeur QElectroTech
  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

Sur Windows ils y viennent petit à petit, bientôt faudra aussi mettre la main au porte-monnaie pour avoir une License et des certificats de confiance, plus ça va et plus installer QET sur Windows  devient pénible...

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Financing macOS machine for improving QElectroTech on MAC M1/M2 arm64

mais si le logiciel n’est pas développé par une entreprise ou à minima une asso, c’est tout de suite plus compliqué.

Oui tu payes plein pot, comme si tu étais développeur indépendant et que c'est ton gagne pain... et la validation des certificats, identité plus complexes..