#73 Add make target to gen c_cpp_properties.json

[AEFeinstein]

Description

Added make gen-vs-properties to generate .vscode\c_cpp_properties.json

Test Instructions

Deleted .vscode\c_cpp_properties.json, ran make gen-vs-properties, and validated the output.

Ticket Links

#73

Readiness Checklist

• I have run make format to format the changes
• I have compiled the firmware and the changes have no warnings
• I have compiled the emulator and the changes have no warnings
• I have run make cppcheck and checked that cppcheck_result.txt has no warnings for the changes
• I have added doxygen comments to any code used by more than one Swadge mode. This includes /*! \file comments with Design Philosophy, Usage, and Example sections for new headers.
• I have run make docs and checked that doxy_warnings.txt has no warnings for the new code

[Brycey92]

Output is still doing some oddities with UNIX-style paths on Windows:

{
    "configurations": [
        {
            "name": "esp32s2",
            "includePath": [
                "${workspaceFolder}/main/**",
                "${workspaceFolder}/components/**",
                "C:\Users\Bryce\esp\esp-idf/components/**"
            ],
            "defines": [],
            "compilerPath": "/c/Users/Bryce/.espressif/tools/xtensa-esp32s2-elf/esp-12.2.0_20230208/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc",
            "compileCommands": "${workspaceFolder}/build/compile_commands.json",
            "cStandard": "c17",
            "cppStandard": "c++17",
            "intelliSenseMode": "gcc-x86"
        }
    ],
    "version": 4
}

Do we have the ability to replace this call with something that puts out Windows paths?

[AEFeinstein]

Ah, looks like it's using msys2's 'which' to find that path to the compiler. There isn't a nice env var to get the compiler unfortunately. I wonder if there's some better way to find the compiler in a cross platform way...

…

On Thu, Nov 2, 2023 at 3:43 PM Bryce Browner ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In makefile <#111 (comment)> : > +################################################################################ + +PROPERTIES_FILE=./.vscode/c_cpp_properties.json + +gen-vs-properties: + @echo "{" >> $(PROPERTIES_FILE) + @echo " \"configurations\": [" >> $(PROPERTIES_FILE) + @echo " {" >> $(PROPERTIES_FILE) + @echo " \"name\": \"esp32s2\"," >> $(PROPERTIES_FILE) + @echo " \"includePath\": [" >> $(PROPERTIES_FILE) + @echo " \"\$${workspaceFolder}/main/**\"," >> $(PROPERTIES_FILE) + @echo " \"\$${workspaceFolder}/components/**\"," >> $(PROPERTIES_FILE) + @echo " \"${IDF_PATH}/components/**\"" >> $(PROPERTIES_FILE) + @echo " ]," >> $(PROPERTIES_FILE) + @echo " \"defines\": []," >> $(PROPERTIES_FILE) + @echo " \"compilerPath\": \"$(shell which xtensa-esp32s2-elf-gcc)\"," >> $(PROPERTIES_FILE) Output is still doing some oddities with UNIX-style paths on Windows: { "configurations": [ { "name": "esp32s2", "includePath": [ "${workspaceFolder}/main/**", "${workspaceFolder}/components/**", "C:\Users\Bryce\esp\esp-idf/components/**" ], "defines": [], "compilerPath": "/c/Users/Bryce/.espressif/tools/xtensa-esp32s2-elf/esp-12.2.0_20230208/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc", "compileCommands": "${workspaceFolder}/build/compile_commands.json", "cStandard": "c17", "cppStandard": "c++17", "intelliSenseMode": "gcc-x86" } ], "version": 4 } Do we have the ability to replace this call with something that puts out Windows paths? — Reply to this email directly, view it on GitHub <#111 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABYODARYLK3C35NY22DN6LYCPZUXAVCNFSM6AAAAAA62IRLGOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOMJRGEYTAOJTGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>