How to tell Xcode a f1.s file is for Intel assembler and f2.s file is for Arm assembler ?

Or equivalent of "C" #if TARGET_CPU_ARM64 #elif TARGET_CPU_X86_64 #endif directive in assembler

Partial solution: let d_tst the directory holding main.c, arm.s, intel.s and source_c a folder of other C files cd d_tst gcc main.c intel.s ./source_c/.c -o x86_app -target x86_64-apple-macos10.12 gcc main.c arm.s ./source_c/.c -o arm_app -target arm64-apple-macos11 lipo -create -output universal_app x86_app arm_app But this work only for command tool with terminal. How to make a universal application with Xcode project and gui (and intel.s, arm.s)? Or to link in a such 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

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 ?

My apology: forget the last reply. Using the Remove button and re-enter the bundle name\ID solve the problem.

Sorry, the picture does not appear in the post !

OK. Fom the web page link I will try "Fix an app built with Xcode" first and if it doesn't work I will try "Fix an app built outside of Xcode". Thanks a lot for the link.

[quote='796643022, DTS Engineer, /thread/760125?answerId=796643022#796643022'] I wanna take a step back and ask about your overall goal. You mentioned Transporter, which suggests that you want to ship your app on the Mac App Store. Is that correct? [/quote] Exactly. Thank you for the web links.

You mentioned Transporter, which suggests that you’re building your app outside of Xcode. Is that correct? No. Is there an other way to submit an Apple application ? you must sign your code with an Apple-issued code-signing identity A certificate ? I really appreciate your help. Thank you.

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

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"

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.

..../sources/qs_arm.s Command CompileC failed with a nonzero exit code

..../sources/qs_arm.s Command CompileC failed with a nonzero exit code Other way to get more explicit detail ?