osx-arm #37
Assignees
Labels
enhancement
New feature or request
Comments
|
This is developed in .net 6.0 and it does not support osx-arm, only osx-x86, and as far as I know (I don't use MacOs) any x86 application should be supported in arm machines using Rosetta 2. Have you tried this using Rosetta 2 and found any problem? If that's the case then please open a bug and I will check for it. Cheers. |
|
I didn't try it for logicanalyzer. Looking at https://dotnet.microsoft.com/en-us/download/dotnet/6.0 it seems like there is arm support for dotnet. |
|
Well, this is a happy coincidence, I just updated VS2022 from version 17.3 to 17.4.4 to add support for the new .net 7.0 SDK and now it lets me to build packages targeting osx-arm64, in fact I have now a ton more of targets like linux-arm64 (it had only arm in the previous version), windows-arm (besides windows-arm64) and so on, it seems that the framework indeed do support it but was Visual Studio the one that was not letting me to target them, not sure if it was my installation that was screwed or that the target has been added recently. I will create the packages with the next release. Cheers. |
|
New release launched with many new targets including MacOSX-ARM64 |
|
I just downloaded the zip - but while it does not start at all. |
|
Need more info as I don't have any mac around to test it... |
|
TBH there isn't much to share. Executing as privileged user "isn't really a thing" on macOS. This is on 12.6.3 on arm. |
|
"sudo" is "superuser do", what means to execute the program as a user with privileged permissions... that's a *nix thing common to all derivates :) From the message looks like something killed the app, not an app crash. Have you tried the GUI app? This may give a bit more info, maybe this is a problem with .net and arm64, I have never used it so checking if the GUI app causes the same problem can at least point to a direction. Cheers. |
That's why I did it ;)
Maybe it could be signing related. But that would usually pop up a security dialog.
What is "the GUI app"? I can't see anything in the dir that looks like a candidate. |
|
The CLCapture app is a command-line application only, it is for the cases that you may want to use the logic analyzer exclusively with sigrok or you don't have a graphical OS like a linux without any desktop manager, but the real application is the one called "LogicAnalyzer", it is a full fledged GUI for the device and a lot more versatile than the CL. It is all on the releases section but here is the link to the osx-arm64 one: https://github.com/gusmanb/logicanalyzer/releases/download/V2.1.1.0/LogicAnalyzer-2.1.1.0-osx-arm64.zip |
|
Ok, I have found info about the problem, it is in fact a problem with code sign: dotnet/runtime#79267 It has been a long time since I developed anything on mac but if I recall it right you need to have a developer account with Apple to do codesign, and I'm not going to pay 100€ just because apple wants it :P You can try the steps proposed in the solution but if you don't have a developer license I doubt you will be able to sign the application: Cheers. |
|
OK. I didn't realize there are two difference artifact downloads. My mistake! Seems like all IIRC it used to be that an Apple account for signing was free - you could just not submit to the AppStore then. Anyway - at least now it's clear how to get it running :) |
|
There might be an intermediate solution, but I need to learn how to use Github Actions, it provides a build environment and it supports macOS as runner, it will sign the application with a self-signed certificate, it will not run at a first but at least it will show the warning about unknown developer and then from the finder you can open it with the context menu. When I get some time and feel better I will give it a try. Cheers! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The releases only list
osx-x86but theses daysosx-armis really needed as well.Would be nice to also have that option.
The text was updated successfully, but these errors were encountered: