User Profile

Hello - TLDR - Is there any sample code to demonstrate how one goes about creating dedicated XPCServices to wrap ARM and Intel-specific dylibs? We have an app we're looking at moving to a universal binary. In that same app we have a framework that currently wraps R functionality by directly linking to /Library/Frameworks/R.framework/Current . R now has dedicated Intel and ARM builds (https://mac.r-project.org/) After watching the 2020 WWDC session "Port your Mac app to Apple silicon" (https://developer.apple.com/videos/play/wwdc2020/10214/?time=2006), it sounds like, for us to deploy a universal binary I should look at wrapping the R interaction bits into dedicated ARM and Intel XPC services so the appropriate architecture for R will run. Is anyone aware of any sample code or extended documentation demonstrating the ins and outs of how to think about this? Thank you

Hello -Xcode 9.2macOS 10.12.6 (16G1114)Objective-C (no Swift)macOS app with test casesWe have a macOS app we've been working on. Objective-C (with some Obj-C++ mixed in). App compiles and runs fine.We've got a bunch of test cases that worked fine until I updated to Xcode 9.2 (from 8.x). Now I can't seem to get them to compile and run. Totally stumped on why.Messages in the log seem to focus around:Expected a type/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/Headers/XCTestCase+AsynchronousTesting.h:180:52: Expected a typeExpected ';' after top level declarator/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/Headers/XCTestCase.h:190:40: Expected ';' after top level declaratorWhen I look at one of the Xcode tests I'm seeing warnings around the XCTest import#import <XCTest/XCTest.h>Shows the warning "Could not build module XCTest"I don't believe I've changed anything (other than upgrading to XCode 9.2).For giggles I created a whole new project (Objective-C as well), created a test target and a test class - no problem - everything worked fine. The issue seems to be contained to my existing app.I read the note re: Swift 4 from (https://developer.apple.com/library/content/releasenotes/DeveloperTools/RN-Xcode/Chapters/Introduction.html) that indicated Swift 4 projects may have issues with test cases, but I'm not using Swift at all (as much as I'd love to). Is it possible the same work-around would be appropriate even though I'm not using Swift?Any ideas very much appreciated. Not sure what I did to somehow make the build gremlins unhappy with these test cases.Thank you,Eric