Picking up a compiler's predefined macros in the wave driver
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with the Wave driver and its @filepath handling. Check how predefined macros supplied with -P are parsed, then compare that path with the compiler-output form of #define lines. Done means the driver can read the file through @filepath and process those definitions without conversion.
Written by the indexing model from the issue text.
Description
A number of compilers have commands to output the predefined macros for the compiler regardless of any source file and just depending on the command line to the compiler. The output is always of the form for each line:
#define SOME_MACRO SOME_EXPANSION
It would be nice if the Wave driver program could just pick up a file of these predefined macros as is, using its @filepath syntax for the file, and process it as predefined macros, rather than having to transform each define from the form above to the wave acceptable form of:
-P SOME_MACRO=SOME_EXPANSION
I understand that I can use some program or regex to transform the compiler's output file to the form which the wave driver accepts, but for convenience sake it would be nice if the wave driver accepted the first form above.
- Dominant language
- C++
- Stars
- 29
- Forks
- 56
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 4
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from boostorg/wave
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
context::set_language does not correctly set __cplusplusPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Similar issues
-
Make Catch2 optional when `RDK_BUILD_CPP_TESTS=OFF`Possibly taken @pechersky claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dice-group/dice-hash#111 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
MerginMaps/mobile#4741 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ros-perception/image_pipeline#1198 ·