Make all #includes relative to the including file

This allows <Lib$Dir>.tboxlibint to be removed from our command line include path. Henceforth, clients of this library also won't need to put it (or C:tboxlibint) in their command line include paths either. It also means that when building the library, only local copies of header files are used (as opposed to a mixture of local and exported copies, as previously).

objects/h/DCS

 #ifndef __DCS_h
 #define __DCS_h
 
-#include "objects/window.h"
+#include "window.h"
 
 /* ----------------------------------------- DCS templates ----------------------------------------- */
 

objects/h/Quit

 #define __Quit_h
 
 #ifndef __toolbox_h
-#include "objects/toolbox.h"
+#include "toolbox.h"
 #endif
 
 

objects/h/colourdbox

 #define __ColourDbox_h
 
 #ifndef __os_h
-#include "os.h"
+#include "../os.h"
 #endif
 
 #ifndef __window_h
-#include "objects/window.h"
+#include "window.h"
 #endif
 
 #ifndef __wimp_h
-#include "twimp.h"
+#include "../twimp.h"
 #endif
 
 /* ColourDbox Templates **************************************************************************/

objects/h/colourmenu

 #define __colourmenu_h
 
 #ifndef __toolbox_h
-#include "objects/toolbox.h"
+#include "toolbox.h"
 #endif
 
 /* Colour Menu Templates ************************************************************************/

objects/h/fileinfo

 #define __FileInfo_h
 
 #ifndef __os_h
-#include "os.h"
+#include "../os.h"
 #endif
 
 #ifndef __window_h
-#include "objects/window.h"
+#include "window.h"
 #endif
 
 #ifndef __wimp_h
-#include "twimp.h"
+#include "../twimp.h"
 #endif
 
 

[Jeffrey Lee]

I'm confused - why do all the #includes here need updating? When resolving quoted includes, don't compilers generally start by treating it as a relative path, relative to the containing file? So prefixing all of tboxlib's includes with tboxlibint shouldn't be necessary, because regardless of whether C:tboxlibint is on the include path or not the files should always be able to find each other.

Prefixing the paths with tboxlibint means it'll always be using the exported versions of the files, which could be annoying if you're in the middle of working on some changes and want to make sure the code still builds or passes (hypothetical) unit tests.