rename concrete -> linking, combine clang folders

GUIDE.txt

@@ -7,11 +7,16 @@ layer, plugin, and main program.
 
 The examples:
 
-*_concrete - Concrete examples for each operating system I have investigated
-             showing how to setup and use various types of dynamic linking. In
-             these the "base" layer goes through load-time linking, the
-             "plugin" layer goes through run-time linking, and the "main" layer
-              acts as the executable that must bind it all together.
+*_linking - Concrete examples for each operating system I have investigated
+            showing how to setup and use various types of dynamic linking. In
+            these the "base" layer goes through load-time linking, the
+            "plugin" layer goes through run-time linking, and the "main" layer
+            acts as the executable that must bind it all together.
+
+clang_linking - Build scripts that build the *_linking examples with clang.
+                Clang does not require changes to the source in either case.
+                The build lines require some modification on Windows.
+                On Linux clang can be directly swapped out for gcc.
 
 xlist - My prefered solution to the problem posed in the investigation which
         relies only on run-time linking. It uses an xlist to manage the

clang_linking/build_linux_linking.sh

@@ -1,7 +1,7 @@
 #!/bin/bash
 
 # Path setup
-cd ../linux_concrete
+cd ../linux_linking
 src=$PWD
 cd ..
 mkdir -p build

clang_linking/build_win32_linking.bat

@@ -2,7 +2,7 @@
 
 REM: Path setup
 
-cd ..\win32_concrete
+cd ..\win32_linking
 SET src=%cd%
 cd ..
 if not exist "build\" mkdir build