#679 Right-click on <header.h>: CB looks in GCC path first regardless of chosen compiler

[Jannick]

How to reproduce:

• create a new project with, say, standard main file
• change compiler of target Debug to any compiler other than GCC
• right-click on #include <stdlib.h> in main.c

Then header file of chosen compiler (or rather of the compiler associated to the active target) is expected to be opened, but header in path of GCC is opened

Using CB svn11246 (nightly build) on Win10.

[Teodor Petrov]

What is the other compiler?

[Jannick]

x86_64-w64-mingw32-gcc/g++.exe.

[Teodor Petrov]

This is too generic. Version number, link to download, etc, please...

[Jannick]

• MSYS2: https://www.msys2.org/ - rewrite of MSYS with cygwin-like shell
• x86_64-w64-mingw32-gcc.exe (Rev2, Built by MSYS2 project) 7.3.0

Probably relevant here: The nice thing about the msys2 shell is that paths are displayed as, e.g., /c/temp (for C:/temp), while cygwin sticks to /cygdrive/c/temp. Both shells ignore single backslashs, in general, since backslashs are to be escaped by a backslash.

If any piece of info is missing, I am happy to share.

[ollydbg]

create a new project with, say, standard main file
change compiler of target Debug to any compiler other than GCC

The reason here is:
When you create the project, the default compiler is GCC, and after your create the project, CodeCompletion use the Compiler(GCC) to fetch all the compiler build-in search paths, so when you switch the compiler, it won't change the build-in search paths.

I think you can save the project after changing the compiler, and then close the project. Then reopen the project, this time, CodeCompletion will use the new compiler set to fetch the include search paths.