-These should help you to install Quassel IRC from source. Please also have a
-look at the README file!
-
-Quassel IRC provides three binaries: quasselcore, quasselclient, and
-quassel. While quasselcore and quasselclient obviously provide the
-separated core and client functionality, the latter one (quassel) is a
-monolithic version containing both of them for convenience.
-
-Note that quasselcore is no longer being built by default, since it tends to
-confuse users more than it helped. It will be back as soon as we have simple mode
-implemented.
-
-We now use CMake as our build system. CMake supports and encourages out-of-source
-builds, which do not clutter the source directory. You can (and should) thus use
-an arbitrary directory for building.
-
-There is no "make distclean"; "make clean" should usually be enough since CMake
-actually cleans up properly (qmake often didn't). If you really want to get rid
-of all build files, just remove the build directory.
-
-Usually, you will build Quassel as follows:
-
-cd /path/to/build/dir
-cmake /path/to/quassel
+These should help you to install Quassel IRC from source. Note that this focuses
+mostly on building on Linux; please feel free to send patches for build
+instructions on other platforms. We are not familiar with them.
+
+There are three versions of Quassel that can be built:
+
+* quasselcore - The server daemon. Typically runs on a headless server and
+ is permanently online. The core connects to IRC and stores
+ both settings and backlog.
+* quasselclient - The GUI client. Requires a running quasselcore to connect to.
+ Upon connection, the client will fetch all session data and
+ a certain amount of backlog from the core and restore its
+ session almost as if you were never gone.
+* quassel - This standalone version, often called "monolithic" or
+ "mono client", contains both a client and a core and can be
+ used like a "normal" IRC client, without having to setup
+ a server daemon.
+
+Prerequisites
+-------------
+
+Of course, for building Quassel you need the usual set of build tools, for
+example a compiler. The codebase uses the C++14 standard, so a reasonably recent
+compiler is needed:
+
+- GCC 5.0+ (available for most platforms), or
+- Clang 3.4+ (available for most platforms), or
+- XCode 6.0+ (available for Max OS X and based on Clang), or
+- MSVC 19+ (part of Visual Studio 2017 on Windows™)
+
+Other compilers may work, but are not officially supported.
+
+As Quassel is a Qt application, you need the Qt SDK, version 5.5 or higher.
+Furthermore, the Boost header-only libraries (at least version 1.56) and
+CMake 3.5 or later are required. CMake will tell you about any missing
+dependencies when configuring the project.
+
+Compiling Quassel - short version
+---------------------------------
+
+Quassel uses CMake as its build system. The canonical way to build any CMake-
+based project is as follows:
+
+cd /path/to/source
+mkdir build
+cd build
+cmake ..