From: dziekon Date: Fri, 15 Sep 2017 22:02:33 +0000 (+0200) Subject: Fix CDT GCC parser to correctly parse C++ commands X-Git-Tag: v3.1-dev~249^2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e822b3788370d2861869bdade9f0b332d4c01fa3;p=esp-idf Fix CDT GCC parser to correctly parse C++ commands Previously suggested parser command pattern: xtensa-esp32-elf-(g?cc)|([gc]\+\+)|(clang) was incorrect for compilation of c++ files, as it is expanded by Eclipse into or between: xtensa-esp32-elf-(g?cc) ([gc]\+\+) (clang) Additional grouping around existing pattern solves that issue, and helps Eclipse to correctly find ESP-IDF includes. Merges https://github.com/espressif/esp-idf/pull/1005 --- diff --git a/docs/get-started/eclipse-setup-windows.rst b/docs/get-started/eclipse-setup-windows.rst index f8bec31e66..94ee30d342 100644 --- a/docs/get-started/eclipse-setup-windows.rst +++ b/docs/get-started/eclipse-setup-windows.rst @@ -58,7 +58,7 @@ Project Properties * In the list of providers, click "CDT GCC Built-in Compiler Settings Cygwin". Under "Command to get compiler specs", replace the text ``${COMMAND}`` at the beginning of the line with ``xtensa-esp32-elf-gcc``. This means the full "Command to get compiler specs" should be ``xtensa-esp32-elf-gcc ${FLAGS} -E -P -v -dD "${INPUTS}"``. - * In the list of providers, click "CDT GCC Build Output Parser" and type ``xtensa-esp32-elf-`` at the beginning of the Compiler command pattern. This means the full Compiler command pattern should be ``xtensa-esp32-elf-(g?cc)|([gc]\+\+)|(clang)`` + * In the list of providers, click "CDT GCC Build Output Parser" and type ``xtensa-esp32-elf-`` at the beginning of the Compiler command pattern, and wrap remaining part with brackets. This means the full Compiler command pattern should be ``xtensa-esp32-elf-((g?cc)|([gc]\+\+)|(clang))`` Building in Eclipse