Richard is correct. It is important to understand the difference between using angle brackets (<>) and quotes with include directives. The quotes will look for files in the local directory first, which is where the source file is, and then in the compiler's include directory search path. The angle brackets cause it to look only in the compiler's include directory search path. This will determine where the compiler looks for the file.
The statement
#include <SFML/Network.hpp>
tells the compiler to look in the subdirectory
SFML
underneath one of its standard include directories. If that is not where you have that header then you probably need to use the double quotes with it, the
""
s.
You can also add dots to specify the relative path as in :
#include "../../SFML/Network.hpp"
That tells the compiler to look two levels up and then in the
SFML
subdirectory of that level. You would use that if you had a directory structure like this :
-Dev--+--MyProject--+--Source
|
+--SFML
and your code files were in
Source
. Two levels up from
Source
is
Dev
and
Network.hpp
would be in the
SFML
subdirectory of
Dev
.
FWIW, this is essentially what my development directory organization looks like.