Gem will get installed in Ruby inside System library. Or try on 10.11 Mac OSX El Capitan, type: sudo gem install -n /usr/local/bin cocoapods.This guide will also work in macOS Catalina, Mojave, High Sierra and Sierra.The process of setting up Virtual Hosts is done easier in the Terminal either using nano or vi with sudo or as a root user, or you can you a GUI visual editor like BBEdit which allows access to the /private/etc directory by clicking ‘Show Everything” in the open dialog box. To install Android Studio on Windows, proceed as follows: If you downloaded an. Exe file (recommended), double-click to launch it. Zip file, unpack the ZIP, copy the android-studio folder into your Program Files folder, and then open the android-studio > bin folder and launch studio64.exe (for 64-bit machines) or studio.exe. Setting up Virtual Hosts in Apache on on macOS Big Sur is straight forward after you have your local Web Development environment up and running – get your web development up and running first including Apache, PHP and MySQL on macOS following this macOS Big Sur Apache/PHP/MySQL guide here if required.Installation.But the ~/username document root is still compatible.To get around this, you need to add in a vhost for localhost and declare this vhost before any of the others, in the same file: sudo nano /etc/apache2/extra/httpd-vhosts.confDocumentRoot /Library/WebServer/Documents/ Restart Apache sudo apachectl restart Changing the WebServer Default UserOne of the frustrations of using the Users/username/Sites folder for vhosts is the permissions issues with things like updates and authentication.This is because the default webserver user which runs httpd is known as _Find Your User and GroupIn the Terminal use the id command to see your username and group idYou will get a bunch of user groups, you need your primary user uid and group gid names uid=502( admin) gid=20( staff)Change this back in /etc/apache2/httpd.confRestart Apache and now you are running httpd as your local account.That’s it, the guide will also work on macOS Catalina, Mojave, High Sierra and Sierra. Mar 24 17:52 COPYING -rw-r-r- 1 user staff 1008 Apr 15 11:36 READ ME drwxr-xr-x 8 user staff 256 gtk-2.0 drwxr-xr-x 6 user staff 192 Apr 15 11:59 gtk-3.0 Create. Ubuntu Development Setup codingstandards databaseextract.I bought a MacBook Air 16 GB M1 to see how viable it is as a main development machine — here’s an early report after a week of testing. The excitement around Apple’s new M1 chip is everywhere. Sudo nano /etc/apache2/extra/httpd-vhosts.confAn example domain in the file is given of the format required to add in additional domains, just follow this to create your new virtual host: DocumentRoot "/usr/docs/dummy-host.example.com"ServerAlias ErrorLog "/private/var/log/apache2/dummy-host.example.com-error_log"CustomLog "/private/var/log/apache2/dummy-host.example.com-access_log" commonWe can take this example and extend on it, if you wanted a domain named apple.com for example, you can copy the existing text block and edit to suit: ServerAlias ErrorLog "/private/var/log/apache2/apple.com-error_log"CustomLog "/private/var/log/apache2/apple.com-access_log" commonSo in the example above a vhost for apple.com is created and the document root is in the Sites/apple folder, in the text block above I have also added in some log files, what you need to change is the document root location username and domain name to suit your needs. Finish and save the file.Now also you need to map the IP address to be the localhost.Apple’s last experiment with fanless MacBooks was the 12-inch version from 2017, which builds the same project in 41 minutes.Our tests mostly ran just fine, although I found a bug specific to arm64, which we missed before, as we don’t run our tests on actual hardware on CI. For comparison, my Hackintosh builds the same in less than 5 minutes.One can’t overstate how impressive this is for a fanless machine. Compiling the PSPDFKit PDF SDK (debug, arm64) can almost compete with the fastest Intel-based MacBook Pro Apple offers (to date), with 8:49 minutes vs.
Developer Setup On Osx 2017 Install Android StudioSome simulators even make problems on iOS 14 an example of this is iPad Air (4th generation), which still emulates Intel, so try to avoid that one.We were extremely excited to be moving our CI to Mac minis with the M1 chip and are waiting on MacStadium to release devices. Performance also seems really bad, with Xcode periodically freezing, and the whole system becoming so slow that the mouse cursor gets choppy. It seems WebKit crashes in a memory allocator, throwing EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0) (Apple folks: FB8920323). As a workaround, ensure at least one Simulator window is onscreen and visible.Update 3: Great news! The WebKit crash when running on Rosetta 2 will be resolved with a future update in Big Sur.Update 4 (May 2021): This is now fixed with Xcode 12.5 and macOS 11.3. Performance seems acceptable if you restrict parallel testing to, at most, two instances — otherwise, the system simply runs out of RAM and swapping is really slow.Update 2: I’ve heard that the choppy mouse cursor is an Xcode/Simulator bug, and it’s currently being worked on. This isn’t great, but luckily we’re not using WebKit a lot in our current project. With our current schedule, we plan to drop iOS 12 in Q3 2021 and iOS 13 in Q3 2022, so it’ll be a while before we can fully move to Apple Silicon.There is a chance that Apple fixes these issues, but it’s not something to count on — given that this only affects older versions of iOS, the problem will at some point just “go away.”Update: We’re working around the WebKit crashes for now via detecting Rosetta 2 translation at runtime and simply skipping the tests where WebKit is used. ![]() This would likely be really slow, so I wouldn’t count on it.Lastly, 16 GB RAM just isn’t a lot. It remains to be seen if VMware or Parallels include a complete x64 emulation layer. We currently support macOS 10.14 with our AppKit PDF SDK, and macOS 10.15 with the Catalyst PDF SDK, both of which are OS releases that require testing. In a few months, it should be possible to develop and test our Windows SDK with Visual Studio on M1 with reasonable performance results.Running older versions of macOS might be more problematic. Microsoft currently doesn’t sell ARM-based Windows, so getting a license will be interesting.Windows 10 on ARM can emulate x86 applications, and Microsoft is working on x64 emulation, which is already rolling out in Insider builds. Various proofs of concept already exist, and performance seems extremely promising. A lot of effort has been put into loop unrolling and vectorization not everything there is available on ARM just yet.Update: Azul offers macOS JDKs for arm64 — also for Java 8. Gradle creates code at runtime, which seems like a particularly bad combination with the Rosetta 2 ahead-of-time translation logic.I expect most issues will be solved by Q1 2021, but it’ll likely be some more time until all Java versions run great on ARM. JetBrains apps currently work through Rosetta 2 however, building via Gradle is extremely slow. Android StudioIntelliJ is working on porting the JetBrains Runtime to Apple Silicon. Future machines will offer 32 GB options to alleviate this issue.Update: Check out How to run Windows 10 on ARM in QEMU with Hypervisor.framework patches on Apple Silicon Mac. This will be even more problematic with virtual machines running. Os x lion download dmgLarger apps take a longer initial performance hit (e.g. ApplicationsMost applications just work Rosetta is barely noticeable. It’s possible to install an additional (ARM-based) version of Homebrew under /opt/homebrew and mix the setup, as more and more software is adding support for ARM.This isn’t currently a problem (performance is good) and will eventually just work natively. Prefix everything with arch -x86_64 and it’ll just work. ![]() It’ll be much harder to accept the loud, always-on fans though, now that I know what soon will be possible. There’s still a lot to do on the software front to catch up, and the bugs around older iOS simulators are especially problematic.All of that can be fixed in software, and the entire industry is currently working on making the experience better, so by next year — when Apple updates the 16-inch MacBook Pro and releases the next generation of its M chip line — it should be absolutely possible to use an M1 Mac as the main dev machine.For the time being, the M1 will be my travel secondary laptop, and I’ll keep working on the 2,4 GHz 16-inch MacBook Pro with 32 GB RAM, which is just the faster machine. ConclusionThe new M1 MacBooks are fast, beautiful, and silent, and the hype is absolutely justified.
0 Comments
Leave a Reply. |
AuthorTrina ArchivesCategories |