![]() I searched my local Android SDK folder for anycodings_android-ndk std=gnu 11 and tried changing all anycodings_android-ndk occurrences consecutively to find out which anycodings_android-ndk one is the one used in my build process. But why anycodings_android-ndk am I getting these warnings then? And how do anycodings_android-ndk I get rid of them? Update Where could that last -std= flag originate anycodings_android-ndk from? If the above problem description is anycodings_android-ndk not enough to deduce a solution, what anycodings_android-ndk further steps could I take in finding out anycodings_android-ndk the origin? And maybe I got it all wrong and anycodings_android-ndk clang already compiles with C 17. None of the other files in my project anycodings_android-ndk contains code that remotely has to do with anycodings_android-ndk build flags. # Build native_app_glue as a static library If you anycodings_android-ndk don't believe me have a look at the source anycodings_android-ndk yourself. I anycodings_android-ndk searched the code and there is nothing anycodings_android-ndk related to std=* or CMAKE_*_FLAGS. anycodings_android-ndk cmrc_add_resource_library from anycodings_android-ndk assets/CMakeRC.cmake compiles resources. Implementation ':constraint-layout:1.0.1' Implementation fileTree(dir: 'libs', include: ) ProguardFiles getDefaultProguardFile('proguard-android.txt'), And so I don't care anycodings_android-ndk about that part yet. I'm still figuring anycodings_android-ndk out how things work. But I got that anycodings_android-ndk from the NDK sample repository and I'm new anycodings_android-ndk to Android programming. I know that some of the anycodings_android-ndk versions here are outdated. The switch cppFlags in here is the origin of anycodings_android-ndk the second flag from the above excerpt from anycodings_android-ndk the build log. Files involved in the building process My gradle.build Also I want to get rid of anycodings_android-ndk the warnings. Nevertheless I anycodings_android-ndk want "real" C 17 support and not just some anycodings_android-ndk GNU extensions. Also I guess anycodings_android-ndk the fact that it's gnu 11 instead of c 11 anycodings_android-ndk activates some GNU extension that leads to anycodings_android-ndk the situation that I'm only getting warnings anycodings_android-ndk and no errors.īut I can't tell for sure. But I can't figure out where the last anycodings_android-ndk one (-std=gnu 11) comes from and how I anycodings_android-ndk could deactivate or modify it. So I don't really care about the first anycodings_android-ndk one. ![]() I guess that later flags override earlier anycodings_android-ndk ones. I tried to change anycodings_android-ndk them to -std=c 17 and -std=c 1z but with anycodings_android-ndk no success. I know where the second and the third flag anycodings_android-ndk comes from (see below). fexceptions -std=c 1z -Wall -O0 -fno-limit-debug-info -fPIC\ ![]() is anycodings_android-ndk appended to the build flags four times: /bin/clang -Wformat -Werror=format-security -std=c 11 -std=c 1z\ anycodings_android-ndk Currently my code compiles without errors, anycodings_android-ndk but Clang prints the following warning: warning: decomposition declarations are a C 17 extension Therefore clang anycodings_android-ndk needs to be called with -std=c 17. Other Android-related properties do generally indicate whether they are intended for the NVIDIA Nsight Tegra setup, or the NDK, or both (or their name makes it obvious).I'd like to use decomposition declarations anycodings_android-ndk in my Android NDK project. Their documentation should at least be updated to specify under what conditions they are used. For example, (at least) the following target properties seem to only be used in the Visual Studio generator, so presumably they only apply to the NVIDA Nsight Tegra setup:įor someone using just the NDK exclusively, it may not be immediately obvious that none of the above properties are relevant or used. A number of Android-specific properties appear to only be used by some scenarios, but the docs don’t mention this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |