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

How does one build this? #7

Open
glitchie opened this issue Jul 20, 2019 · 6 comments
Open

How does one build this? #7

glitchie opened this issue Jul 20, 2019 · 6 comments

Comments

@glitchie
Copy link

So, I cloned the repo, changed bundle identifier, grabbed Swift 4.2, and it throws no such module 'ZIPFoundation' whenever I try to build it, which I believe is supposed to be in Externals. I tried using Carthage to manually provide it (I followed the instructions from Riley's repository for ZIPFoundation), it shows up in Navigator, however it doesn't seem to work as it still throws the above error. Can someone provide detailed instructions on how one can build Delta from source (Preferably with instructions on how to build the cores)?

@CmdrChaos
Copy link

CmdrChaos commented Jul 20, 2019

cd into External and type "git submodule init". Then cd into ZIPFoundation and type "git submodule update".

When you open Xcode DeltaCore project, switch your scheme to ZIPFoundation and and build it, then switch your scheme to DeltaCore and it will build as well.

@glitchie
Copy link
Author

glitchie commented Jul 21, 2019

I just did that, and now I'm getting Use of unresolved identifier 'SIMD2'; did you mean 'SIDL'? in ThumbstickInputView.swift, on lines 187, 188 and 245. I tried the default Xcode 10.1 toolchain and the Swift 4.2 Snapshot one, both using Swift Language v4.2. I also tried the refactor Xcode suggested (replace SIMD2 with SIDL) which resulted in Cannot call value of non-function type 'Int32'. Any idea how to fix that?

@CmdrChaos
Copy link

So you successfully built ZIPFoundation, and then when you switch back to the DeltaCore Schema you are getting this error? I did not see this issue when building.

@glitchie
Copy link
Author

Yes, this is exactly what I’m saying.

@CmdrChaos
Copy link

Hmm sounds like something wrong in your setup... I did not get that error when building. When did you last pull the updates?

@glitchie
Copy link
Author

glitchie commented Jul 27, 2019

I used the latest commit as of June 21st, which I cloned the day I first posted this issue

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

No branches or pull requests

2 participants