Wt

h1. Using CMake

{{toc}}

In this example we are going to see how to use CMake to compile a very simple Wt project where you have a source directory with all your files
and a build directory to generate your application.

If you don't care where your files are located or you are looking for an even simpler example you can go [[Frequently_Asked_Questions#Q:How_do_I_build_my_newly_written.22Hello_World.21.22_application.3F|here]].

h4. Directory Structure

Before starting make sure that your project main directory (In this example the main directory is called main) looks like this:

main
|
+--source..................you have all your files here

|
+ -- CMakeLists.txt .. a text file where we will write CMake commands (empty)

+--build.................. build directory (initially, this directory is empty)
+--CMakeLists.txt ........ a text file where we will write CMake commands (empty)

h4. CMakeLists.txt in the main directory

These are the contents of the CMakeLists.txt file that you should write on the main directory

CMAKE_MINIMUM_REQUIRED(VERSION 2.6)

PROJECT(WT_EXAMPLE)

SET (WT_CONNECTOR "wtfcgi" CACHE STRING "Connector used (wthttp or wtfcgi)")

ADD_SUBDIRECTORY(source)

• The first two instructions are self descriptive. CMAKE_MINIMUM_REQUIRED checks that you have the indicated version. If you don't include this instruction in your CMakeLists.txt you will be able to continue but you will see a warning message. The second option, PROJECT, simply assigns a name to your CMake project.

• The third instruction is a bit more interesting. SET allows to create variables inside a CMake script. In this case we are creating a variable named WT_CONNECTOR that is going to contain a string value that by default is going to be "wtfcgi". The syntax used here is:

SET(VARIABLE_NAME default_value CACHE type "help message")

• The CACHE options allows to save the value. Next time you run ccmake (as you will see later) the variable will contain the last value that you entered.

• The last instruction in this CMake script is ADD_SUBDIRECTORY. This instruction will delegate the execution of the script to the subdirectory enclosed in parenthesis.

The syntax is:

ADD_SUBDIRECTORY(subdir)

You need to make sure that there is a CMakeLists.txt file in the subdirectory that you are referencing, so that sub CMakeLists.txt will be executed.

In our example as we have one subdirectory (source) we will have a correspondant CMakeLists.txt file in there.

h4. CMakeLists.txt in the source directory

This is an example of the CMakeLists.txt file that goes in the source directory

SET(WT_PROJECT_SOURCE
File1.h
File1.cpp
File2.h
File2.cpp
Main.C
)

SET(WT_PROJECT_TARGET wt_project.wt)

ADD_EXECUTABLE(${WT_PROJECT_TARGET} ${WT_PROJECT_SOURCE})

TARGET_LINK_LIBRARIES(${WT_PROJECT_TARGET} ${WT_CONNECTOR} wt)

INCLUDE_DIRECTORIES(/usr/local/include/Wt)

Let's break this down:

h5. Variables in a CMake script

WT_PROJECT_SOURCE and WT_PROJECT_TARGET are two variables and you can change the names as you like as long as you make sure that you change them everywhere in your script.

h5. SET instruction

The CMake SET instruction allows to associate any number of strings with a CMake variable. The syntax is:

SET(CMAKE_VARIABLE string1 string2 ... stringN)

In our example we have two SET instructions. The first one is allowing us to associate all our source file names with WT_PROJECT_SOURCE. The second SET instruction is associating the string wt_project.wt with WT_PROJECT_TARGET.

h5. ADD_EXECUTABLE instruction

The ADD_EXECUTABLE instruction configures the executable file you are about to compile. The syntax is:

ADD_EXECUTABLE(EXECUTABLE_NAME file1 file2 ... fileN)

However given that we have our source list in the variable WT_PROJECT_SOURCE, we can write:

ADD_EXECUTABLE(EXECUTABLE_NAME ${WT_PROJECT_SOURCE})

In this case we see the way CMake variables can be used. Every time that you want to refer to any variable contents you just need to use the ${} syntax around the variable name.

h5. TARGET_LINK_LIBRARIES instruction

The TARGET_LINK_LIBRARIES instruction allows to link our executable file with the depending libraries. The syntax is:

TARGET_LINK_LIBRARIES(EXECUTABLE_NAME lib1 lib2 ... libN)

In our case we need to make sure that the our executable links to Wt (wt library) and one of the connectors (wthttp library or wtfcgi library). In our example, the connector name is stored in the variable WT_CONNECTOR.

h5. INCLUDE_DIRECTORIES instruction

The INCLUDE_DIRECTORIES instruction adds the given directories to those searched by the compiler for include files. The syntax is:

INCLUDE_DIRECTORIES(dir1 dir2 ... dirN)

For the sake of the example, I have added the directory /usr/local/include/Wt. This is where all the Wt header files live in my Ubuntu installation. However this might not be the case for you and you might want to decipher where these files are in your system. The general solution for this is to use

TODO: Talk about FIND_PACKAGE

h4. Project files/Makefiles generation

Once you are finished editing the source/CMakeLists.txt file you should go to the build directory and type:
cmake ..

You will see the initial CCMake screen on your terminal console:

Page 0 of 1
EMPTY CACHE

EMPTY CACHE:
Press [enter] to edit option CMake Version 2.6 - patch 4
Press [c] to configure
Press [h] for help Press [q] to quit without generating
Press [t] to toggle advanced mode (Currently Off)

Here you need to run the configuration option by pressing [c]

This will take you to the next screen:

Page 1 of 1
CMAKE_BUILD_TYPE

CMAKE_INSTALL_PREFIX /usr/local

WT_CONNECTOR wtfcgi

CMAKE_BUILD_TYPE: Choose the type of build, options are: None(CMAKE_CXX_FLAGS or
Press [enter] to edit option CMake Version 2.6 - patch 4
Press [c] to configure
Press [h] for help Press [q] to quit without generating
Press [t] to toggle advanced mode (Currently Off)

At this point, you need to define the type of build (CMAKE_BUILD_TYPE) you are going to do. Options are:

• Debug
• Release
• RelWithDebInfo
• MinSizeRel

Next we see that the variable WT_CONNECTOR that was defined in the main directory CMakeLists.txt file appears. As stated before, options for this variable are:

• wthttp (Wt connector)
• wtfcgi (FastCGI connector)

Once you are set this properties, for instance selecting Debug and wtfcgi respectively, you need to configure again (by pressing [c]). This time an aditional option [g] appears:

Page 1 of 1
CMAKE_BUILD_TYPE Debug

CMAKE_INSTALL_PREFIX /usr/local

WT_CONNECTOR wtfcgi

CMAKE_BUILD_TYPE: Choose the type of build, options are: None(CMAKE_CXX_FLAGS or
Press [enter] to edit option CMake Version 2.6 - patch 4
Press [c] to configure Press [g] to generate and exit
Press [h] for help Press [q] to quit without generating
Press [t] to toggle advanced mode (Currently Off)

At this point you press [g] to generate your project. This step takes care of the files that need to be generated in order to compile your project on the platform you are working on. For example if you were working on Visual Studio under Windows, then the project and solution files would be generated. On Linux you will see that there is a set of Makefiles that you will use to compile your project.

After pressing [g] you will end up in the build directory again. This time we just do a regular make. The output should be something similar to this:
cg

make
[ 50%] Building CXX object src/CMakeFiles/App.wt.dir/App.cpp.o
[100%] Building CXX object src/CMakeFiles/App.wt.dir/Main.C.o
Linking CXX executable App.wt
[100%] Built target App.wt

Now your application is ready to go. To execute your application you need to follow the guidelines for the case where you are using the built-in Wt server or any FastCGI supporting web server.

h4. Summary

Well that is basically it. I hope this had been helpful to understand a little bit more what CMake is about. As this is the first version of this document please feel free to make any comments, suggestion, or corrections.

If you want to learn more about the different instructions that CMake offers I advise you to visit:

• Pau Garcia's CMake slides (http://www.elpauer.org/stuff/learning_cmake.pdf)
• The CMake documentation webpage (http://www.cmake.org/cmake/help/cmake2.6docs.html)