Updated the version number.

CMake/Modules/TBTKVersionInfo.cmake

@@ -1,8 +1,8 @@
 #Avoid printing setting and printing information multiple times.
 IF(NOT TBTK_VERSION_DEFINED)
 	SET(TBTK_VERSION_MAJOR 1)
-	SET(TBTK_VERSION_MINOR 0)
-	SET(TBTK_VERSION_PATCH 3)
+	SET(TBTK_VERSION_MINOR 1)
+	SET(TBTK_VERSION_PATCH 0)
 	SET(
 		TBTK_VERSION
 		${TBTK_VERSION_MAJOR}.${TBTK_VERSION_MINOR}.${TBTK_VERSION_PATCH}

README.md

@@ -198,7 +198,7 @@ They should therefore only be considered for use by experienced developers.
 ## Installation
 ```bash
 git clone http://github.com/dafer45/TBTK
-git checkout v1.0.3
+git checkout v1.1.0
 mkdir TBTKBuild
 cd TBTKBuild
 cmake ../TBTK

doc/InstallationInstructions.md

@@ -29,13 +29,13 @@ TBTK can be downloaded from github, which is done by typing
 TBTK is still in a phase where changes to the core API may occur, even if most core components are relatively stable by now.
 To be able to know that a particular application compiles also in the future, it is recommended that application developers work against one of the public releases.
 A list of releases and their name tags can be found on https://github.com/dafer45/TBTK/releases.
-To use a particular version, for example v1.0.3, execute the following from the TBTK source folder
+To use a particular version, for example v1.1.0, execute the following from the TBTK source folder
 ```bash
-	git checkout v1.0.3
+	git checkout v1.1.0
 ```
 It is recommended to store a note inside projects using TBTK that tells against which version of the library it has been compiled.
 This makes it possible to anytime in the future checkout the exact same version of TBTK and recompile an application developed against it.
-If a named version such as v1.0.3 is not used, the developer should instead remember the exact git hash.
+If a named version such as v1.1.0 is not used, the developer should instead remember the exact git hash.
 
 # Install TBTK {#InstallTBTK}
 ## Unix like operating systems such as Linux and Mac OS