![]() Another browse through stack returned the sobering news: Xcode cannot yet build some Silicon Chip dependencies. I am using the library Firebase/Firestore in one of my projects, which was missing now. Once I installed everything, I went back into Xcode and built the project. Great! After a browse through stack, the solution that worked for me was installing ffi with gem install ffi. I got a long list of error messages and the final note saying Oh no, an error occurred. The problems started arising when I ran pod install. Great! So I went into the terminal and ran pod deintegrate, which is always the first command to run when anything goes wrong with dependencies. I was bamboozled by 38 compiling / build errors. Running my Xcode projects.Īs usual, I pulled all my projects and opened one. I was happy to see that homebrew became M1 compatible in February and was thus available natively! Once homebrew was installed, installing cocoapods and all other libraries was easy and working without a problem. The most essential is the third-party packages manager homebrew. Installing packagesįor my iOS development flow, I require a few packages and libraries to get me going. All of these, except Spotify, were already compatible with the M1 processor and ran without Rosetta 2 (the emulator for running x86–64 applications on the M1). I immediately installed all my most important apps like iTerm, Slack, and Xcode. I received my new Mac with much excitement with the all-new M1 Silicon Chip a few days ago. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |