No; the nearest approach is a collection of -I
options on the command line.
Further, if you use SFML, the recommended notation is #include "SFML/System.hpp"
; that's what you should write in your code. Then you fix the compilation environment so that -Idependencies/sfml/include
is included in the compilation, or you use symlinks (if they're portable enough) to manufacture sub-directories like SFML
in the main directory that contains your project's headers.
When software packages like SFML are installed, the headers will be placed into a directory — normally /usr/local/include
by default, and usually in a sub-directory under there. That is, there would be a directory /usr/local/include/SFML
which would contain the SFML headers. The chances are the same is true of other software packages. You should install these headers in some location under your build area so that the headers can be found as normal — you'll simply specify the base include
directory under which the headers are found. (Note: when you install the Bullet Physics library, the headers are placed into a directory .../include/bullet
with various sub-directories underneath that, so it too follows this convention.)
Doing otherwise means fighting the system, and when you fight the system, you end up losing. It is harder work than simply going with the flow.