Making it such that osquery doesn't need to be built in the repo "build"
subdirectory. gentable.py now accepts a positional argument which
indicates the output (which is calculated by cmake) so they don't have
to agree on a destination ahead of time.
I used CPack to generate deb package files from the CMake "install"
target. What this means is, whatever would get installed my "make
install" will get installed by the deb.
"make package" on ubuntu will generate a file named: `osquery-$VERSION-$DISTRO.$ARCH.deb`
Consider the following example:
```
root@vagrant-ubuntu-trusty-64:/vagrant/build# dpkg --info osquery-0.0.1-trusty.amd64.deb
new debian package, version 2.0.
size 11311330 bytes: control archive=350 bytes.
207 bytes, 9 lines control
102 bytes, 2 lines md5sums
Package: osquery
Version: 0.0.1
Section: devel
Priority: optional
Architecture: amd64
Installed-Size: 43369
Maintainer: marpaia@fb.com
Description: osquery is an operating system instrumentation toolchain.
```
I like the pattern of the root CMakeLists.txt being the parent file
which sets global parameters and the children doing their level of
compilation.
I also updated the OS X pkg creator.
