Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating MOAI Xcode sample project settings so they compile again #124

Open
wants to merge 10 commits into
base: mindsnacks-dev
Choose a base branch
from

Conversation

aab29
Copy link

@aab29 aab29 commented Dec 23, 2020

The first step in getting MOAI to run with MetalANGLE on the mindsnacks-dev branch is to get MOAI's sample Xcode projects (included in this repository) to compile again. They haven't been updated in years, and stopped working a long time ago. 🏛️ Many changes were made to the moai-dev develop branch since we forked off from it. 🍴 I've been trying to figure out which changes to copy over from the Xcode projects on the main fork to make our Xcode projects compile again. ⬅️

This PR is what I think is the minimum set of changes needed to get just the iOS Xcode project to run. 📱 The iOS project currently compiles and installs on my iPhone, but it won't open when I install from my work computer. ⚠️ I'm sure this is happening because I don't have my provisioning profiles set up correctly, but it should work fine once we sort that out. 🔀

I haven't tried getting the "osx" project to work yet, but I should be able to follow similar steps to get it working. 💻

Note that in order to get the iOS sample project to run, you must copy the contents of a Lua example folder from the samples directory into xcode/ios/lua. I think the anim-basic folder is a good one to use because it doesn't try to do anything fancy. 🚫🧐

Also note that this PR does not include any of the changes needed to get MetalANGLE running. 🙅 Those changes are on a separate branch on top of this PR that I'm still working on... but I'm optimistic that I can get something working soon. 🤞🤞

Also also note that we'll want to do some cleanup before we merge this PR. 🧹 I just wanted to get the changes out there for now. 👐

…et will compile again on macOS. Needed to raise the deployment target, remove references to `libcrypto.dylib` and `libssl.dylib`, set `LIBRARY_SEARCH_PATHS` to `$(SDKROOT)/usr/lib/system`, and set the `customWorkingDirectory` value in the `Run` scheme to a Lua sample from the `$PROJECT_DIR/../../samples/anim/anim-basic` directory. Phew!
…13.0`. Believe it or not, we are no longer using iOS `4.3`! I also set changed the architectures to `$(ARCHS_STANDARD)` since `$(ARCHS_STANDARD_32_BIT)` hasn't worked for years.
…ker Flags" entry under the "Linking" section of the MoaiSample Build Settings tab.
… `Build Settings` group under `libmoai.xcodeproj`.
…the unique ID of each touch event, and that no longer compiles, use the last 32 bits of the 64-bit pointer, and pass that in.
…e preventing the app from compiling. We'll probably need to do something else to clean them up later.
…gets), and under the "Deployment (unnamed domain)" section, setting the `IPHONEOS_DEPLOYMENT_TARGET` to `13.0`.
@@ -505,33 +564,41 @@
1D6058940D05DD3E006BFB54 /* Debug */ = {
isa = XCBuildConfiguration;
buildSettings = {
ALWAYS_SEARCH_USER_PATHS = NO;
DEVELOPMENT_TEAM = JG69W4K637;
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this development team id for a personal account? If so we might want to unset that.

@stevenmah
Copy link

Wanted to check in on what the development plan is for this update project.

Should we have a base feature branch that we should be merging these incremental updates into and keep it as Hold until everything is updated and ready to go?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
3 participants