-
Notifications
You must be signed in to change notification settings - Fork 196
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
PCRE2 requires C99 support #1041
Comments
I tried to build on my own machine. When I used android-toolchain-gcc.xml I got this error, but android-toolchain-clang.xml succeeded. Edit: actually I got the same error in a different file. Didn't even make it as far as compiling pcre. |
-std=c99 on the toolchain breaks some other c code (SDL) . I think -std=gnu99 might be best for all gcc based toolchains (android - others too?) without breaking anything. Or -std=c99 on the PCRE flags only. Not sure if windows will like this or not. |
Adding the flag to the toolchain produces a huge number of "valid for C/ObjC but not for C++" warnings when compiling other libraries. Let's try the PCRE-specific approach. |
MSVC doesn't recognise the I used the MSVC_VER to limit the usage to prevent it from being passed to msvc: #1042. Could you see if the android build works with this patch in #1042? @player-03
If it's added to the toolchain, it should be added as a |
Testing now.
Actually I added it as a |
Having this same issue did you ever figure it out? |
This is fixed in the git version of hxcpp but there hasn't been a new release to haxelib yet. You can install from git using:
|
thanks but I already tried that. I specified more at openfl/lime#1682 |
It looks like this is your error: #1064 |
This is from Lime's github actions android builds:
Seems like the new version of pcre from #1037 doesn't compile with older c standards.
It looks like this is why this commit was necessary? 27210f2 @hughsando
Maybe we can set the flag only for the pcre sources? Otherwise, it requires adding the c99/c11 flag to the remaining toolchains.
The text was updated successfully, but these errors were encountered: