files. It takes a simple template file and generate the necessary code to use the defined tracepoints in your application.
The section TEMPLATE FILE FORMAT describe the content of the template file.
-Currently, the tool can generate the .h and .c associated to your
+Currently, the tool can generate the .h, .c and .o associated to your
tracepoint. The generated .h can be directly included in your application.
-You need to compile the .c into a .o, .a or .so at your choice and
-link it with your application. Refer to the UST documentation for the
+You can let the tool generate the .o or compile the .c yourself.
+You can compile the .c into a .o, .a or .so at your choice and
+link it with your application.
+Refer to the UST documentation for the
advantages and disadvantage of each form.
To compile the resulting .c file, you need to add the options
-"-llttng-ust -I."
+"\-llttng-ust \-I.".
+Note for C++ support: although an application instrumented with
+tracepoints can be compiled with g++, tracepoint probes should be
+compiled with gcc (only tested with gcc so far).
.SH "OPTIONS"
.TP
.BR "\-o, \-\-output"
Specify the generated file. The type of the generated file depend on the file
-extension (.h, .c).
+extension (.h, .c, .o).
This option can be specfied multiple times to generate different file type.
.PP
-When no output is specified de default files are generated with the same base filename as the template file. The default files are: .h, .c.
+When no output is specified de default files are generated with the same base filename as the template file. The default files are: .h, .c, .o.
.SH "TEMPLATE FILE FORMAT"
-The template file, which has the usual extention \fB.tp\fP, contains a list of
+The template file, which has the usual extension \fB.tp\fP, contains a list of
TRACEPOINT_EVENT definitions and other optional definition entries like
TRACEPOINT_LOGLEVEL.
(See lttng-ust(3) for the complete list of available definition.)
ctf_string(message, text)
)
)
+.SH "ENVIRONMENT VARIABLES"
+.PP
+When the tool generate an .o file, it will look for the following environment variables
+.PP
+
+.PP
+.IP "CC"
+Specifer which C compiler to use. If the variable is not specified, the
+tool will try "cc" and "gcc"
+
+.IP "CFLAGS"
+Flags directly passed to the compiler
.SH "SEE ALSO"
.PP