Try to separate globals needed by libstp and globals needed by the
stp executable. This turned out to be quite difficult because the
current design is horrific (see FIXMEs added)!

It has been necessary to disable the 'h' flag to vc_setFlag() and
vc_setFlags() to do this. This doesn't really matter because
vc_setFlag() and vc_setFlags() NEED TO BE REMOVED!
Allow to create a static binary for Linux using -DBUILD_STATIC_BIN=ON
As per @delcypher the set(STP_STATIC_LIBRARY ON) is not needed

Thanks, it's cleaner now
Only '-static' is needed and if not provided it's the best we can do

Only the "LINK_SEARCH_START_STATIC" was needed, and there is no need to
unset it, as it's only for one target. Furthermore the setting only
affects what cmake things of the default behaviour of the linker, and
cmake doesn't save its old assumption so it cannot be restored anyway.

The "-static" linker flag is still needed though, otherwise we cannot
get gcc_s and other libraries to link statically:

http://stackoverflow.com/questions/3762057/cmake-how-to-produce-binaries-as-static-as-possible
Fixing missing LINK_SEARCH_END_STATIC setting for stp target
Merge pull request #116 from msoos/static_binary

Allow to create a static binary for Linux
Teach CMake to create usable python package for the python STP interface
and to run tests against this package.
Teach CMake to install python package for STP inferface.

By default we try to guess where to install by asking
${PYTHON_EXECUTABLE} where its python library directory is (this for the
case that a virtualenv python is being use). This might might be a
little counter-intuitive because ${CMAKE_INSTALL_PREFIX} is completly
ignored during this process so a user without root access may end up
with a failing install by default.  A user can override what is detected
by setting the newly added PYTHON_LIB_INSTALL_DIR CMake option.
Disable python tests by default because the tests hit STP assertion
failures. This needs to be fixed properly at some point.
Merge pull request #105 from delcypher/python_cmake

Allow new python interface to be tested and installed. The tests are disabled though due to hitting STP assertion failures.
Avoid static build temporarily due to fail of cmake for generating makefile when cross compile using i686-pc-mingw32
Support mingw cross-compiler for building Windows binary using linux as a development platform
support -std=gnu++0x option for gcc 4.6.3 which does not recognize -std=gnu++11
Teach travis to build multiple configurations. This is done by using
TravisCI's build matrix feature. We set an environment variable to
indicate which configuration we want.

Unfortunately there doesn't seem to be a direct way to have options
set with -D to CMake be set instead with environment variables. So
instead we use a wrapper script to set the configuration.
Fix running of API tests when BUILD_STATIC_BIN is enabled.
Try to fix the broken STATIC_BINARY build in Travis when using clang.
It's most likely an issue with the old clang and ld on Ubuntu 12.04LTS
Disable python interface when building configurations that only
build libstp as a static library otherwise we get configuration
errors.
Merge pull request #125 from delcypher/multiple_travis_configurations

Teach travis to build multiple configurations. This is done by using
Large reorganisation. Header files have been split out into their own
include/stp folder and library code has been moved into to the relevant
folders in lib/ . The stp tool has been moved in tools/stp.

This layout mimics that of the LLVM project which is a very well
organised project.

The motivation for doing this was the disgusting relative #includes
that were all over the place. These made compiler errors/warnings hard
to read and made it impossible for an application external to STP use
the header files!

``include/stp`` is supposed to contain public header files that would be
installed so that STP can really be used as a library. This probably
isn't done correctly right now because

- Some headers that should be internal should be in lib/
- The use of the extlib-abc, extlib-constbv mess this up. We should
  really be using these as a proper external library that the user
  has installed and build against those header files. We also shouldn't
  be bundling this library inside STP!
- The minisat and cryptominisat2 SAT solvers are mostly in lib/.
  This feels messy, again we should really building against installed
  versions of this library and not bundle the library inside STP!
Fix running C-api tests