It’s basically a main function which prints HelloKodo! and exits. In this
example, we include a particular RLNC codec defined in the following header
file:

1

#include<kodo_rlnc/full_vector_codes.hpp>

The include is not used however. Its only purpose is to detect whether or not
the include paths for the kodo-rlnc library are configured correctly.

The remaining two files are needed to build the executable.
The waf file is a complete standalone build system,
whereas the wscript is the recipe used by waf to build our example.
The wscript contains information regarding dependencies and build targets.
The simplest way to get started is to copy the hello_kodo files to a folder
where you want to develop your application, and then run the standard waf
commands in that folder (the cp command is Unix-only):

The build system will download all dependencies, compile some static libraries
and finally the example. You can find the compiled executable in the waf build
folder, which depends on your operating system:

Linux: ./build/linux

Mac OSX: ./build/darwin

Windows: ./build/win32

You can directly run the executable by executing the appropriate command: