-
Notifications
You must be signed in to change notification settings - Fork 306
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
Can there be an easier way to get a full version of the code? #12
Comments
The code is from Spring 2018, and at that time it built correctly. Since then a new version Xcode and Swift has come out, and broken all sorts of existing code. Given how much code came with the book, I doubt it will be updated.
I share your disappointment, but the constant changes with Swift and Xcode make maintaining open source code a huge burden.
If you really want to see a successful build, you would need to install the prior version of Xcode, and then it might build.
Chris H
… On Oct 27, 2018, at 7:23 AM, Krisjanis Gaidis ***@***.***> wrote:
Hello,
I bought the book. I clicked the download link, pressed the .epub and it opened in Books. 👍
I bought the videos. I clicked the download link, pressed the .m4v and it opened in Quicktime Player. 👍
I cloned this repository. I clicked on the Xcode project and got build errors. And then it started a chain nightmare of updating Carthage, fixing brew, fixing macOS permissions, reading about how Carthage maybe only builds for latest Swift version (4.2) while RxSwift.framework is built for 4.0.2 through git issues etc. etc.
Can the dependencies be uploaded, or can there be a step-by-step guide where I can 100% make sure that the project builds? I feel like the code is part of the "product" and it's sad that everyone who clones it has to potentially go through hours of re-configuration.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#12>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAh86-SY7XFE5gyc9_9qA55qro7Tx783ks5upF40gaJpZM4X9bZg>.
|
I understand, and agree, that it's not easy to update these types of things and that constant changes do not make it easy to maintain. I would side with the opinion that eventually this would be too much to ask for. I do feel like this process can be made easier, at least for a little bit of time. For example, I think if I download Xcode 9, and the dependencies are also uploaded/checked-in to the git repository, I think I will be able to run the project. Could be wrong, but this feels like an easy fix: provide some help to download Xcode 9 in the README, and upload dependencies. Or even if I can't get it to build, I can maybe browse some of the source code from the dependencies to get a better picture. In fact, the origin for wanting to get the dependencies was to read docs for |
To anyone having issues getting the carthage build to work, I got the carthage build (for MVVM-C) working for the newest XCode (10.1) by editing the cartfile as follows:
|
The above worked for me! Thanks @NielsNorskov |
Hello,
I bought the book. I clicked the download link, pressed the
.epub
and it opened in Books. 👍I bought the videos. I clicked the download link, pressed the
.m4v
and it opened in Quicktime Player. 👍I cloned this repository. I clicked on the Xcode project and got build errors. And then it started a chain nightmare of updating Carthage, fixing
brew
, fixing macOS permissions, reading about how Carthage maybe only builds for latest Swift version (4.2) whileRxSwift.framework
is built for 4.0.2 through git issues etc. etc.Can the dependencies be uploaded, or can there be a step-by-step guide where I can 100% make sure that the project builds? I feel like the code is part of the "product" and it's sad that everyone who clones it has to potentially go through hours of re-configuration. Some of this maybe will be unavoidable (ex. getting an older version of Xcode), but at least that's the only step I would have to take.
(P.S. The particular project that I mentioned is MVVM-C)
The text was updated successfully, but these errors were encountered: