A build system using GNU make is provided for environments where Bazel is not available.

Shared libaries and applications can be built from their directories, with output to bin/ and obj/ directories under the project root.

General make help:

$ make help

Debug and release builds:

$ make # or make debug

$ make release

submodules

Using the GNU make system requires several submodules to be available under the import/ directory.

To initialize the submodules:

$ git submodule update --init --recursive

To refresh the submodules:

$ git submodule update --init --remote --recursive

googletest

Running unit tests requires a git submodule snapshot of googletest.

Now can build and run unit tests, for example from net/unittest directory.

code coverage (gcov)

Code coverage instruments the code using the –coverage -fprofile-arcs -ftest-coverage options, and links with -lgcov. The gcov application can be used to analyze the code.

An example using gcov from the examples/net directory:

$ make cleanall
$ make gcov
$ LD_LIBRARY_PATH=../../bin ../../bin/ntest_d -I # list interfaces
$ LD_LIBRARY_PATH=../../bin ../../bin/ntest_d -T google.com 443 # test connect to google
$ pushd ../../net/ # go to the source directory for net
$ gcov -fjmr -o ../obj/sccnet_d * # create .gcov output files
File 'net_if.cc'
Lines executed:91.53% of 118
Creating 'net_if.cc.gcov'
$ less net_if.cc.gcov # take a look
$ rm *.gcov # gcov leaves these files around
$ popd
$ make cleanall # get rid of all the instrumented object files