You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since clang is the only supported compiler in the official NDK, this is a problem. It seems to have not come up yet mainly because of developing with the CrystaX NDK.
I intend to focus on getting this working following the upcoming release.
Following #1103, clang is used by the jni components (sdl2, sdl2_image etc.) but other recipes still use gcc. However, it's promising that clang seems to work fine where it does get used, and it shouldn't be too hard to add clang compiler paths in p4a.
Activity
inclement commentedon Aug 26, 2017
This issue might just be the same as #1095 .
inclement commentedon Aug 29, 2017
Following #1103, clang is used by the jni components (sdl2, sdl2_image etc.) but other recipes still use gcc. However, it's promising that clang seems to work fine where it does get used, and it shouldn't be too hard to add clang compiler paths in p4a.
AndreMiras commentedon Apr 16, 2019
@inclement this is working now right?
Julian-O commentedon Nov 18, 2023
@inclement: Is this working now?
misl6 commentedon Nov 18, 2023
Absolutely yes!