![]() While searching for a arm64 compatible JDK back in 2021, the Azul Zulu JDK build popped up first. The first thing we install as Java developers on a new machine is a JDK. I'll refer to the traditional Intel/AMD processors as 圆4 (you may find the following synonyms: x86_64, amd64). Note: Throughout this article, both arm64 or aarch64 refer to the Apple M1 chip. This article will share my initial pitfalls when working with the Apple M1 and a collection of valuable tricks and workarounds for developing and testing Java applications. To solve those problems (not my main intent, but I told myself so) and experience if that processor is really that fast, I decided to buy the MacBook Pro. ![]() I was first shocked to encounter hardware incompatibilities in 2021. I had my first contact with the Apple M1 when one of my course students raised an issue that the build doesn't pass on Apple's new flagship laptop. Xcode: 13.2.It's been almost a year since I've bought the MacBook Pro M1 ( arm64 processor) for my daily Java development as a freelance consultant. arch -x86_64 gem install -user-install ffi -enable-libffi-alloc Other than that, I’m working on a fresh workstation. Previously (on RN 0.66) I had run the following commands to install x86_64 ffi, which allowed me to successfully run pod install on M1. I’m running on zsh (M1 macOS 12.1), so I ran the following but the warning remained: env /usr/bin/arch -arm64 /bin/zsh -login Run "env /usr/bin/arch -arm64 /bin/bash -login" then try again. ![]() May result in mixed architectures in rubygems (eg: ffi_c.bundle files may be x86_64 with an arm64 interpreter) Emulated x86_64 is slower than native arm64 Bootstrapped a new react-native project and got the following warning on pod install: Do not use "pod install" from inside Rosetta2 (x86_64 emulation on arm64). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |