Compiling for 2009 iMac

Hello everyone. Hoping someone can point me in the right direction. The computer Id like to use: Model A1225 iMac 24" Early 2009 9.93GHz 2 Duo (E8335) 4Gb SODIMM NVIDIA FeForce GT 120 (256Mb) Machine: iMac9,1 Running macOS El Capitan version 10.11 At the moment Im trying xcode 8.2.1 There is a page on compiling the cores and so forth, with a video utilising command line and text suggesting use xcode Im going around in circles, so perhaps if I supply screen shots of the errors, someone can help…

Anyone have any suggestions? Thank you

In your top image it looks like you’re trying to build RetroArch Cg, which requires additional libraries. Just try building the RetroArch target and it should hopefully go better.

For xcodebuild/xcode-select, try running xcode-select -r to reset it back to the default path; it shouldn’t be pointing at the command line tools.

Thank you! OK, tried resetting the paths and made no difference. So turned my attention to using Xcode. First picture shows the 2 projects there, including the one you mentioned with the dependencies. I gather its not a simple matter of removing one. As seen in the next picture though, several xcode projects are on offer, and I thought perhaps that being for different platforms, so I chose what seemed an appropriate one for my old machine. The resulting errors are show in the third image.

I guess that while Ive used code including C before, this is a brand new platform and unfamiliar IDE for me.

Does the version of xcode look appropriate to you (see my orig cry for help), and I selecting the wrong thing? Looks like I need my hand held for this stage.

this is a brand new platform and unfamiliar IDE for me

Ah, ok. Yes the version of Xcode should be fine. Doing it inside of Xcode it going to be a lot easier than with xcodebuild so let’s stick with that.

There are many .xcodeproj files (and one .xcworkspace) that are lightly documented at https://docs.libretro.com/development/retroarch/compilation/osx/#retroarch-compilation. In your first picture in your original post and the first picture in this latest post, you were using RetroArch.xcodeproj, which for versions of macOS earlier than 10.13 is the best one to use. (The ones with _iOSnn are all for versions of iOS and can be ignored here.)

In your second post, first image, at the very top next to the window management buttons, there is a play button, a greyed out stop button, and then a toolbar that in your photo says “RetroArch Cg”. It is a selectable menu and you can change it to just “RetroArch” from there.

Aha! Thanks for the pointers - I have a successful build! very cool. Um, I gather that its not deployed, or it hasn’t taken it to the app stage where I can run it? Or am I not looking in the right places?

So there are a few things you can do now.

One option is just to run it directly from Xcode by hitting the triangle Play button at the top left in the first picture on your second post. That’s a typical developer workflow.

In your first picture on your second post you are pointing at the Products, and now RetroArch.app should be black instead of red. If you right-click on it there should be an option to “Reveal in Finder” or similar. From there you would be able to run it directly outside of Xcode. You could also copy it into the /Applications folder from there.

One other thing to check is whether you built it as a debug or release build. There really isn’t that much difference between the two except that release has a few extra compiler optimizations so may run slightly faster. In Xcode there should be an option to “Edit Scheme” (typically ⌘-Shift-comma) and change the Build Configuration from Debug to Release.

By default a build produced from Xcode will not have all of the assets, core info files, etc., so you will need to use the Online Updater to download everything.

All good Eric, I really appreciate the time your spending on this. I located the Debug/Release option and the location of the compiled file. Does the error dump below mean anything to you? In the meantime I’ll look at the debugging options in there…

Process: RetroArch [713] Path: /Users/USER/Library/Developer/Xcode/DerivedData/RetroArch-elsaicpimnmiwsadvbilrmvsaykk/Build/Products/Release/RetroArch.app/Contents/MacOS/RetroArch Identifier: com.libretro.RetroArch Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: RetroArch [713] User ID: 501

Date/Time: 2024-03-10 14:48:50.899 +1030 OS Version: Mac OS X 10.11.6 (15G22010) Report Version: 11 Anonymous UUID: 35891D29-EA19-3C88-76B2-E9877A10137C

Time Awake Since Boot: 2300 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

kernel messages:

VM Regions Near 0x7fff7df4e0a8 (cr2): __LINKEDIT 00007fff62ae8000-00007fff62afd000 [ 84K] r–/rwx SM=COW /usr/lib/dyld –> Submap 00007fff70000000-00007fff80000000 [256.0M] r–/rwx SM=PRV process-only VM submap unused shlib __DATA 00007fff7ab67000-00007fff7f111000 [ 69.7M] rw-/rw- SM=COW system shared lib __DATA not used by this process

Thread 0 Crashed: 0 dyld 0x00007fff62a75000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit): rax: 0x000000000000000d rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007fff5d7a6bd0 r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000 r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 rip: 0x00007fff62a75000 rfl: 0x0000000000000201 cr2: 0x00007fff7df4e0a8

Logical CPU: 0 Error Code: 0x020000f4 Trap Number: 133

Binary Images: 0x7fff62a74000 - 0x7fff62aaba47 dyld (???) <6B9CD3BA-2D60-3629-A0CB-AB810F55E8DD> /usr/lib/dyld

External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 1111 thread_create: 0 thread_set_state: 0

VM Region Summary: ReadOnly portion of Libraries: Total=308K resident=0K(0%) swapped_out_or_unallocated=308K(100%) Writable regions: Total=11.1M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=11.1M(100%)

                            VIRTUAL   REGION 

REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= Process Corpse Info 2048K 2 STACK GUARD 56.0M 2 Stack 8192K 2 VM_ALLOCATE 4K 2 VM_ALLOCATE (reserved) 872K 2 reserved VM address space (unallocated) __DATA 240K 3 __LINKEDIT 84K 2 __TEXT 224K 2 mapped file 9144K 4 shared memory 8K 3 =========== ======= ======= TOTAL 76.3M 14 TOTAL, minus reserved VM space 75.5M 14

Model: iMac9,1, BootROM IM91.008D.B08, 2 processors, Intel Core 2 Duo, 2.93 GHz, 2 GB, SMC 1.45f0 Graphics: NVIDIA GeForce GT 130, NVIDIA GeForce GT 130, PCIe, 512 MB Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.102.30) Bluetooth: Version 4.4.6f4, 3 services, 27 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en1 Serial ATA Device: WDC WD6400AAKS-40H2B0, 640.14 GB Serial ATA Device: OPTIARC DVD RW AD-5670S USB Device: USB Bus USB Device: Hub in Apple Pro Keyboard USB Device: USB OPTICAL MOUSE USB Device: Apple Pro Keyboard USB Device: BRCM2046 Hub USB Device: Bluetooth USB Host Controller USB Device: USB Bus USB Device: IR Receiver USB Device: USB 2.0 Bus USB Device: USB 2.0 Bus USB Device: Built-in iSight Thunderbolt Bus:

Code Signature Invalid typically means that the OS is expecting the app to be properly signed by a developer, but it doesn’t think it is.

In the OS System Settings app there should be something like a Security preference pane that you can use to relax that restriction.

Alternatively, in Xcode’s preferences, there should be an Accounts tab that will let you log in using your Apple ID. After you’ve logged in, select the RetroArch project in the Xcode navigator (at the top of the tree in the first picture on your second post) and there should be a tab for Signing & Capabilities that you can use to change the Team or Developer to your Apple account.