manpage -> man pages

[lttng-docs.git] / contents / using-lttng / instrumenting / c-application / lttng-gen-tp.md

diff --git a/contents/using-lttng/instrumenting/c-application/lttng-gen-tp.md b/contents/using-lttng/instrumenting/c-application/lttng-gen-tp.md
index 78f4dfa555fc9bc3b6457ac79ddf5e09e37fa19b..1ac4ad02cc73a635e09a3a5ddc750cc4e503ad05 100644 (file)
--- a/contents/using-lttng/instrumenting/c-application/lttng-gen-tp.md
+++ b/contents/using-lttng/instrumenting/c-application/lttng-gen-tp.md
@@ -10,7 +10,7 @@ source file or a precompiled object file) with its header file.
 
 `lttng-gen-tp` should suffice in [static linking](#doc-static-linking)
 situations. When using it, write a template file containing a list of
-`TRACEPOINT_EVENT()` macro calls. The tool will find the provider names
+`TRACEPOINT_EVENT()` macro calls. The tool finds the provider names
 used and generate the appropriate files which are going to look a lot
 like `tp.h` and `tp.c` above.
 
@@ -20,8 +20,15 @@ Just call `lttng-gen-tp` like this:
 lttng-gen-tp my-template.tp
 </pre>
 
-`my-template.c`, `my-template.o` and `my-template.h` will be created
+`my-template.c`, `my-template.o` and `my-template.h` are created
 in the same directory.
 
+You may specify custom C flags passed to the compiler invoked by
+`lttng-gen-tp` using the `CFLAGS` environment variable:
+
+<pre class="term">
+CFLAGS=-I/custom/include/path lttng-gen-tp my-template.tp
+</pre>
+
 For more information on `lttng-gen-tp`, see
-<a href="/man/1/lttng-gen-tp" class="ext">its manpage</a>.
+<a href="/man/1/lttng-gen-tp" class="ext">its man page</a>.