Should I use relative include paths for my project, or place the include-directory on the include path?
In my project, I currently use relative paths to include my files, which admittedly doesn't change often. However, it yields pretty weird include patterns, because I usually nest my files in alot of folders. For example, in my current project I have network/server/myfile.hpp . It needs to include common/log.hpp . Current I use #include "../../common/log.hpp" which is pretty verbose, but works. If i instead add my main include directory on the path, I could simply include "common/log.hpp" . I know this question might be more about preference than anything else, but is there any objective pros