Updated Mac XCode Projects Take 2 #247
Conversation
Take two because last time I accidentally swapped the XCode project files
plz work
Yeah I figured that was what was gonna get me. Try again
How hard do I need to specify the `\`
|
Was tired and hungry last night so I forgot to mention this resolves #221 |
|
Hold on a sec the fullscreen doesn't look right |
Google says it's because the app hasn't been signed. |
Well if you build it yourself then there's no need to use that command. And if you were to upload it to for example Google Drive and redownload it, all you will need to do is hold Ctrl, click the app, and select open to allow the option to open anyways. However, for some reason if you download it via the GitHub actions autobuild, you need to use the |
If this doesn't work I'll just revert it
This reverts commit 7b4967e.
|
Nope, I don't think it does |
|
The xattr command is just telling your local machine to trust the unsigned app. It won’t affect any other machines. The only solution that doesn’t require workarounds is actual code signing, but I don’t think you’re going to find a developer who wants to put their paid signing keys on a public GitHub build bot. The right-click open trick is also being removed in macOS 15 that comes out next week. The only options for working builds would be getting a dev to sign them for you, building it yourself because it signs for the machine you build on, or the getting an unsigned build and running the xattr command to set the trusted attribute. |
I was wondering if we could use self signed certificates for this as well, which imo would be good enough for such a project. Do you know if this is possible on macOS? |
Self signed certs are basically what you’re using when you build locally without a bot. No, on a buildbot that is going to be equivalent to not being signed at all since the cert isn’t going to be trusted by the end users. And the certs on macOS come from Apple, it’s not like windows where they can come from any certificate authority trusted at the OS level. |
|
... Are you serious? |
So last time I accidentally broke it by swapping the xcode projects for the Dependencies and the Engine. This time, I suffered an ungodly amount of time figuring out how to apply compiler flags and getting the autobuild to work, also after messing up my forks having to redo everything.
This pull request the RSDKv3 mac builds up to speed with the latest GitHub commit. This includes updated icons, making sure the build doesn't crash for me, and being able to easily building signed frameworks for Ogg, Vorbis, and Theora. The new README also includes how to use and modify the CXX Flags.
The majority of the code is from @Sappharad's fork, although I did get permission beforehand to use it to do a pull request. I I have edited and removed some of the changes from the fork.
Please test this on Windows before you pull because while not much should have changed, I can't test it on Windows because I don't know how to compile it for Windows while on a Mac.
As for the autobuild, if you download the
v3-mac.zipit will say that the app is broken. That is wrong. To be able to use it, runxattr -cr RSDKv3.appassuming your current directory is where the app is. Or just typexattr -crand drop the app into the Terminal.