wpilibsuite / wpilibsuite/native-utils
Make C++ standard user-selectable
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5
- Forks
- 30
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 4
Description
C++ dashboard applications can use newer compilers and standard versions than C++17. native-utils appends the C++17 flag after the user's flags, so it always overrides the standard version to C++17.
I tried changing the standard version by adding it.cppCompiler.args.add('-std=c++20') and it.cppCompiler.args.remove('-std=c++17') to build.gradle. The former added the C++20 flag, but the latter didn't stop the C++17 flag from being added, since I assume that happens later.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the native-utils Gradle plugin behavior described in the issue and the build.gradle configuration using cppCompiler.args. Trace where the -std=c++17 flag is appended after user arguments. Done means a user-selected standard such as C++20 is not overridden by the plugin's default flag.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100