Update README

.gitignore

@@ -1,4 +1,5 @@
-*.user
+CMakeCache.txt
-*.o
+CMakeFiles
 Makefile
+cmake_install.cmake
 metacall

CMakeLists.txt

@@ -0,0 +1,16 @@
+project("metacall")
+
+add_executable(
+    metacall
+    mc_binding.cpp
+    mc_buffer.cpp
+    mc_client.cpp
+    mc_prefab.cpp
+    mc_protocol.cpp
+    mc_serial.cpp
+    mc_server.cpp
+    mc_socket.cpp
+    mc_stream.cpp
+    mc_token.cpp
+    testing.cpp
+)

README.md

@@ -1,13 +1,13 @@
 # Metacall
 
-A while ago I needed to find a simple cross-platform IPC library to use for one of my projects. After a good amount of
+Many winters while ago I needed to find a simple cross-platform IPC library to use for one of my projects. After a good
-searching, I was disappointed to discover that although there were lots of libraries for handling IPC, all were very
+amount of searching, I was disappointed to discover that although there were lots of libraries for handling IPC, all
-"enterprisey", had a lot of dependencies, and generally difficult to integrate into my simple console application.
+were very "enterprisey", had a lot of dependencies, and were generally difficult to integrate into my simple console
-Basically, I wanted to use something that was easier than raw sockets/pipes, but conceptually simpler than a gigantic
+application.  Basically, I wanted to use something that was easier than raw sockets/pipes, but conceptually simpler than
-platform-specific monster like [WCF](http://en.wikipedia.org/wiki/Windows_Communication_Foundation). Before long, I
+a gigantic platform-specific monster like [WCF](http://en.wikipedia.org/wiki/Windows_Communication_Foundation). Before
-came to the realization that there was nothing left to do but write to this library for myself. I called it "Metacall"
+long, I came to the realization that there was nothing left to do but write to this library for myself. I called it
-to reflect the use of C++ template metaprogramming in its implementation, combined with the notion of "calling"
+"Metacall" to reflect the use of C++ template metaprogramming in its implementation, combined with the notion of
-functions over the TCP/IP sockets.
+"calling" functions over the TCP/IP sockets.
 
 Metacall was designed with the following principles in mind:
 
@@ -18,7 +18,3 @@ Metacall was designed with the following principles in mind:
     [sockets](http://en.wikipedia.org/wiki/Network_socket).
 *   Do prefer simplicity over a complex feature set.
 *   Do keep boilerplate code requirements to a minimum.
-
-This page is still a work in progress, check out the [code repository](https://github.com/FooSoft/metacall/) for the
-time being!
-