Default search directory

[J_Will]

Hello,
Many tutorials describing how to link a library to a project indicate that you must specify the compiler and linker paths in the build options.
However, I note that if we do not specify these access paths and the headers and lib.a are positioned in the include and lib directories of MinGW then the program is correctly built. The question is: Where these default access paths are specified in Code::blocks ?

Thanks.

[Grit Clef]

Do you mean the default headers and libraries that MinGW can read automatically? If not, then you do need to specify their paths except that you have already specified them in the search paths.

[J_Will]

For example, when I link GLEW (for opengl) to a project:
1) I copy all the header GL/*.h in C:\Program Files (x86)\CodeBlocks\MinGW\include
2) I copy libglew.a in C:\Program Files (x86)\CodeBlocks\MinGW\lib
3) I add glew in the liker settings of the project
4) I build the project and it works fine.

I don't have to add include and lib paths in the search directories of the project.
It seems that Code::block searches in these directories by default...
 

[Grit Clef]

It's not finished by CodeBlocks, because you copied those files to MinGW's include and lib directory. The compiler will search those directory by default.

[J_Will]

Ok thank you. Thi sis due to the compiler. That means many tutorials are wrong

[sodev]

No, the tutorials are right, DO NOT copy any custom files into these default compiler directories unless you are looking for BIG trouble.

[stahta01]

Ok thank you. Thi sis due to the compiler. That means many tutorials are wrong

The tutorials that tell you to copy files into the compiler toolchain locations are likely written by newbies or idiots, sometimes both.

Unless the directions are on how to create a compiler toolchain then copying files into the toolchain folders are almost always a bad idea!

Tim S.

[J_Will]

Wow don't be so vindicative both of you

No trouble if you copy custom files into include and lib folders of the compiler. We just have to know where the compiler is looking for those files during compilation.
But you are right, it's not very clean to do like that.

In fact I noticed that Code::blocks is delivred with a very old version of GCC (GCC8.1 !!). And with this version of GCC, we need to precise the include and lib path in the search directory otherwise it doesn't work (so the tutorials are right). But with a more recent version of GCC (I use GCC10.3) it is not necessary.

Thank you for all your replies.