Post

Replies

Boosts

Views

Activity

Reply to Xcode Arm vector assembly error
"Compile qs_arm.s (arm64)328"CompileC /Users/alain/Library/Developer/Xcode/DerivedData/QS-cibiavwrwfecqvgtkmfwdqiatgoh/Build/Intermediates.noindex/QS.build/Debug/QS.build/Objects-normal/arm64/qs_arm.o /Users/alain/Desktop/QS_univ/sources/qs_arm.s normal arm64 assembler-with-cpp com.apple.compilers.llvm.clang.1_0.compiler (in target 'QS' from project 'QS')c45c92378389c641^755897378389c641^-190"/Users/alain/Desktop/QS_univ/sources/qs_arm.s:159:2: error: unrecognized instruction mnemonic, did you mean: and, ands? vand q8, q8, q10 ^ Command CompileC failed with a nonzero exit code 1(21%IDEActivityLogMessage5@48"Command CompileC failed with a nonzero exit code-
2w
Reply to Transporter and entitlement
So things have changed from previously? No except now I distribute within Xcode (I no longer use Transporter): To create a distribution-signed app using the Xcode app: [from "Export an app from Xcode" in your link "Creating distribution-signed code for macOS" ] 1- Select your app’s scheme. 2- Choose Product > Archive. 3- In the Archives organizer, select the archive created in step 2. 4- Click Distribute App. 5- Choose the appropriate distribution method. For example, to create a notarized app that you send directly to your customers, choose Direct Distribution. 6- Click Distribute. No issues no errors. Because earlier you were reporting an “App sandbox not enabled” error? No longer see this error. Is "App Store Version Release" must be set "Automatically release this version" ? What is the next step ? Thank you.
Oct ’24
Reply to Transporter and entitlement
I am sorry, I am late to reply. Are you building this product with Xcode? Yes. I follow the instructions from "Export an app from Xcode" in your link "Creating distribution-signed code for macOS" "Validate App" and "distribute App" report no issues no errors. But "Apple Store Connect -> macOS App" still show "Prepare for Submission" message. In "App Store Version Release" which one must be selected: "Manually release this version" or "Automatically release this version"
Oct ’24
Reply to Transporter and entitlement
lsbom ./com.abirtz.lnc.pkg/Bom ... ./lnc.app/Contents/Resources/lnc.entitlements 100644 0/0 311 30787299 ... codesign -d --entitlements - /Applications/lnc.app Executable=/Applications/lnc.app/Contents/MacOS/lnc [Dict] [Key] com.apple.security.app-sandbox [Value] [Bool] true [Key] com.apple.security.files.user-selected.read-write [Value] [Bool] true [Key] com.apple.security.get-task-allow [Value] [Bool] true
Sep ’24
Reply to Bundle ID and Certificates
Those are the same thing. So I assume that Bundle ID in "Certificates, Identifiers & Profiles" must be copied in Xcode "Target" "Signing & Capabilities" ? I do a mistake in the Bundle ID in "Certificates, Identifiers & Profiles" (developer web site). How can I change this Bundle ID ?
Apr ’24
Reply to How to compile arm .s, x86 .s (and .c, .m ) files to a single universal .app in Xcode project ?
Solution: insert .s assembly code between .if TARGET_CPU_ARM64 and #if TARGET_CPU_X86_64 test_cpu.c #include <stdio.h> #include "TargetConditionals.h" #include "test_cpu.h" extern int64_t add_test_asm(int64_t, int64_t); char buf[128]; int64_t a, b, sum; void test() { #if TARGET_CPU_ARM64 a = 4; b = 70; sum = add_test_asm(a, b); snprintf(buf, 128, "CPU is ARM64, %llu + %llu = %llu", a, b, sum); #elif TARGET_CPU_X86_64 a = 40; b = 7; sum = add_test_asm(a, b); snprintf(buf, 128, "CPU is X86_64, %llu + %llu = %llu", a, b, sum); #endif } test_cpu.h extern char buf[]; extern void test(void); add_arm.s file #include "TargetConditionals.h" .if TARGET_CPU_ARM64 .globl _add_test_asm .align 4 _add_test_asm: add x0,x0,x1 ret .endif add_intel.s file #include "TargetConditionals.h" #if TARGET_CPU_X86_64 .globl _add_test_asm .align 4 _add_test_asm: movq %rdi,%rax addq %rsi,%rax retq #endif
Jul ’23