We don't compile fdbmonitor with thread sanitizer instrumentation, since this
appears to change its behavior (it no longer seems to restart killed
processes). fdbmonitor is single-threaded anyway.
1. `-isystem ../flow/-lpthreads` was appearing as an include flag
Due to an apparent mistake of specifying CMAKE_THREAD_LIBS_INIT
as a system include. The correct way to do this is to link
against Threads::Threads, which was already done below.
2. fdbmonitor wouldn't link due to missing pthread_once
So it also needs to link against Threads::Threads
Up unto here this code is only very rudiemantery tested.
This is a firest attempt of making cpack more user-friendly.
The basic idea is to generate a component for package type so
that we can have different paths depending on whether we build
an RPM, a DEB, a TGZ, or a MacOS installer. The cpack package
config file will then chose the correct components to use.
In a later point this should make it possible to build these
with `make packages` and the ugly iteration with calling cmake
between each package would be obsolete. While this solution is
a bit more bloated, it is also much more flexible and it will be
much easier to use.
Another benefit is, that this will get rid of all warnings during
a cpack run
This changes makes a cmake build check for an existing
versions.h file in the source directory before it builds
anything else. If it finds it it will fail the build.
This is to prevent confusion when someone tries to use cmake
on a source directory where the old build system was used
before (as this is not supported).
