-
Notifications
You must be signed in to change notification settings - Fork 9
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
ARM64 support #4
Comments
This would indeed be nice. Unfortunately there isn't the single ARM64 build which would then work on all ARM64-based platforms (in the same way as there are separate windows and linux builds although both use x86-64). First of all, PhysX needs to support the target platform / system. This is the case for Android and the Universal Windows Platform (including Windows 10 for ARM). Mac OS is also supported but, as far as I know, not yet the ARM version. There is no dedicated Raspberry Pi target but it should be possible to use the regular linux target and disable the x86 optimizations (SIMD mostly). Anyway, we would need to target each of these platforms separately which is quite a bit of work. So maybe one day, but first I would concentrate on extending features for the existing targets. |
Just bumping this as M1 Macs get more adopted and will definitely be the norm at some point in the future! |
Bumping this aswell, hope to see support for arm64 linux |
I just published an updated version of the PhysX 5 bindings ( |
Seems to be working fine! ARM support for Linux would be much appreciated as well (for certain VR headsets). |
Linux/arm64? |
Hi! This is not something I use, but I thought it may be fitting for the library to provide an ARM64 build. It is getting pretty popular in various fronts like the Apple M1 (destined to replace the x86 Macs), Raspberry Pi has been ARM64 capable for years, I think there are a bunch of tablets and stuff running Windows 10 for ARM, the overbearing presence of Android, etc.
As I said, I have no use of it, but I thought it may be relevant to provide an ARM64 build down the line.
The text was updated successfully, but these errors were encountered: