   #include syntax giving me troubles.Quotations vs Braces.
  #include <gdk/gdkcolor.h>The above does not work for me. Visual Studio 2003 refuses to find it. However, this does work. #include "gdkcolor.h"I am trying to compile some stuff, some demos of sdl apps, and almost all of them have include directives in the form of <blah/blah.h>. I don't know the difference between using Quotations and using braces in an include. Could you help me there? I know they are header files that contain code for compliation, but the difference between "blah" and <blah > is, I do not know. And why is there two names inside a <   > directive with a slash seperating them? What does that mean compared to a single blah.h?How do I make Visual Studio accept the < blah / blah.h > format. I certainly don't want to rewrite all the include directives in these demos. Help. Thx   
  blah/blah.h specifies the file blah.h in the directory blah.  When you use the angle brackets, it searchs the include path (/usr/include on most UNIX systems, on Windows it varies quite a bit), while the double quotes search both the current directory and the include path.   ;  I am on a windows system by the way. So what do I need to do to get my files to be found with < directory/file.h >?Where does the directory start from however?I guess I'd like to know where it is searching.<C:/gtk/gtk.h>, is pefectly clear to me where it is searching. However < gtk/gtk.h> isn't as clear. Where is it at?[Edited by - foxtrotalpha on December 10, 2005 12:48:15 AM];  You need to create a directory in your include directories that has those files in it. The directory varies a lot from compiler to compiler. Check out the configuration for the IDE or we could probably tell you where it is if you tell us which compiler you're using.   ;  I'm using Visual Studio 2003. Strange, if I dump the GTK file into my include directory within the Visual Studio 2004 install directory, it functions correctly. Now that is weird.   ;  I use the same IDE and my default include directory is this:C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7You could create the directory there and place your headers inside that newly created directory.   ;  I guess I don't understand why the directory "gtk/gtk.h" indicates the include folder of your visual studion 2003 install. Strange.If I don't use "directories" inside of the include directive, I am fine, beceause I have them set up inside the options menu of VS. Strange.   ;Include files are looked for on the include pathIf you #include "foo", the preprocessor will first look in the current directory, then on the include path.If you #include <foo>, the preprocessor will only look on the include path.#include <foo/bar> will look for bar in a foo subdirectory of the directories specified on the include path. If the include path is (unix-style, but similar for windows) /usr/include; /usr/local/include, then the file could be either /usr/include/foo/bar or /usr/local/include/foo/bar.Generally, the default include path is specified in an environment variable (VS 7.1 appear to set INCLUDE, but I don't know if it is actually used).Command-line preprocessors (and, indirectly, IDEs) can add to the include path on a case-by-case basis with the -I or /I switch.VS lets you configure the include path under Tools->Options->Projects->VC++ Directories.;  I have VC++ 6 (don't laugh everyone!), and you can just set the directories that are checked when you include something with < > Just go to Tools->Options then select the "Directories" tab. Then is has a drop-down called "Show directories for", and from there it is straight forward.   ;  Like Fruny explained, in order for <>'s to "work" you need to specify the include paths that Visual Studio will search for headers.In Visual Studio 6, I believe it's under Tools->Options->Directories, but correct me if I'm wrong (it's been a while).In Visual Studio .NET it's under Tools->Options->Projects->VC++ Directories.The reason why it works if you place your headers in the Visual Studio include folder it's because that particular folder is under the Visual Studio include paths.""'s will search the current directory first and then the rest of your Visual Studio include paths.   