c compiler cannot create executables mac

Go under “Signing and Capabilities” and set things how you need them to be for code signing.Xcode will link to it, and set it to be copied to your app bundle and signed when building. in the build settings for your app, in the General tab, hit the + button under “Frameworks, Libraries, and Embedded Content”, hit Add Other, then add the amework from before.copy amework to the same folder as your app’s.create a new Mac App project in Xcode, with Objective-C as the language.You just make a regular Mac app in Xcode, but rip out the Mac app stuff (since SDL provides its own):

You can also use xcodebuild with the supplied Xcode projects if all you’re after is command-line building: xcodebuild -scheme Framework DSTROOT='/path/to/where/you/want/it' archive Just set the minimum macOS version to something reasonably modern that isn’t the latest version (like 10.13) and you’ll cover 90+% of Mac users. Every Mac shipped since about 2008 has a 64-bit CPU, and every version of macOS since 10.6 (2009) has been 64-bit, so the need hasn’t existed in a long time. IMHO it’s not really worth trying to build fat binaries with a 32-bit slice anymore. Maybe the paths are wrong? (it’s kinda weird that script still uses GCC, since it’s just a symlink to clang nowadays maybe that you’re using actual GCC is the problem?)įor dynamic linking, the instructions you linked specify that you have to set the dylib’s install_name if you’re gonna ship it alongside a binary that isn’t in an app bundle (you should absolutely 100% ship your game in an app bundle on macOS). One of the earlier messages is that the C compiler doesn’t work.

C compiler cannot create executables mac