Add subproject example.

Added example how to structure projects with libraries as subprojects
were the library also can have their own example and/or unittests.
Changed error message to be more specific

Also suggest possible workaround.
Merge pull request #236 from leidegre/patch-2

Changed missing VS error message to be more specific
FreeBSD build fixes.

Use clang (default nowadays)
Fix missing stdio.h include.
Add basic (non-OSX) clang toolchain for FreeBSD.

Change hello world to build on FreeBSD.
Support GCC & Clang precompiled headers

The MSVC Precompiled Header switches allow one very little room for how to
go about using them, but GCC/Clang are much more flexible. It is not
immediately obvious exactly how to use precompiled headers with GCC just
by reading the documentation, because there are some subtle issues
regarding how one names the .pch files, and how one includes them, such as
with <pch.h> or "pch.h".
I believe I have found a solution that should work for most project
setups, so that they work equally well on MSVC, GCC, and Clang.

These rules need to be obeyed in order
for precompiled headers to work:
1. The directory where your precompiled header file lives must be in the
Includes list of your project.
2. You must always include the file using the same path, and with quotes,
not angle brackets.
For example, the following does not work:
- #include <pch.h>
And neither does this:
- #include "../pch.h"

I have extended the pch example so that the pch.h file takes long enough
to compile that one can see the time difference with the naked eye.

I struggled for quite a long time until I discovered this:
The path that you send the compiler via the -include flag can be the
complete path to the location of the .gch file. One's first attempt is
naturally to try "-include pch.h". This fails in several subtle ways, one
of which is a GCC (4.8.2) segfault. What we now do instead is to use
something like
-include t2-output/.../pch.h
So long as there is a pch.h.gch file in there, then the compiler will
correctly inject that as the precompiled header, and you won't be subject
to path relativity issues. This seems obvious in hindsight, but it took a
long time to discover.
Create project directory named by version of visual studio.
Add --start-group/--end-group to linker to help with circular dependancies.
It's meant to be slower but for even our most complex project it didn't seem to slow the build/link time at all.
Add new tools: intel compiler, microsoft assembler & luajit