3 .\" Author: [see the "AUTHORS" section]
4 .\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
6 .\" Manual: barectf manual
7 .\" Source: barectf 2.2.1
10 .TH "BARECTF" "1" "11/15/2016" "barectf 2\&.2\&.1" "barectf manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
25 .\" disable justification (adjust text to left margin only)
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
31 barectf \- Generate C99 code that can write native CTF packets
35 \fBbarectf\fR [\fB--prefix\fR=\fIPREFIX\fR] [\fB--dump-config\fR]
36 [\fB--code-dir\fR=\fIPATH\fR] [\fB--headers-dir\fR=\fIPATH\fR] [\fB--metadata-dir\fR=\fIPATH\fR]
37 [\fB-I\fR \fIPATH\fR]\&... [\fB--ignore-include-not-found\fR] \fICONFIG\fR
41 The \fBbarectf\fR command generates C99 code, that itself can write Common Trace Format <http://diamon.org/ctf> packets natively, out of a YAML configuration input file \fICONFIG\fR\&. The full documentation of barectf is available on the project\(cqs website <http://barectf.org>\&.
43 A prefix is used to scope the generated file names, as well as the generated function names, macro names, structure names, and so on\&. By default, this prefix is \fBbarectf_\fR\&. It can be overridden by the configuration file, and ultimately by the \fB--prefix\fR option\&.
45 By default, all generated C and CTF metadata files are written to the current working directory\&. The \fB--code-dir\fR, \fB--headers-dir\fR, and \fB--metadata-dir\fR options are used to control where the generated files should go\&.
47 You can add directories to be searched into for inclusion files, before the default search directories, by using the \fB-I\fR option one or more times\&.
49 By default, if an inclusion file is not found while processing the configuration file \fICONFIG\fR, an error is emitted\&. You can instruct \fBbarectf\fR to continue silently instead by providing the \fB--ignore-include-not-found\fR option\&.
51 To view the effective YAML configuration file used for generating the C and CTF metadata files, after having processed all inclusion files, use the \fB--dump-config\fR option\&.
54 \fB-c\fR \fIPATH\fR, \fB--code-dir\fR=\fIPATH\fR
56 Write C source files to directory
58 instead of the current working directory\&.
63 Dump the effective YAML configuration file, after all inclusions are processed, to the standard output\&.
66 \fB-H\fR \fIPATH\fR, \fB--headers-dir\fR=\fIPATH\fR
68 Write C header files to directory
70 instead of the current working directory\&.
73 \fB--ignore-include-not-found\fR
75 Do not consider as an error inclusion files that are not found: continue silently\&.
78 \fB-I\fR \fIPATH\fR, \fB--include-dir\fR=\fIPATH\fR
82 to the list of directories to search into for include files\&. The default list of directories is the current working directory, followed by the directory containing the provided, "standard" inclusion files\&.
85 \fB-m\fR \fIPATH\fR, \fB--metadata-dir\fR=\fIPATH\fR
87 Write CTF metadata file to directory
89 instead of the current working directory\&.
92 \fB-p\fR \fIPREFIX\fR, \fB--prefix\fR=\fIPREFIX\fR
94 Override the configuration file\(cqs prefix with
95 \fIPREFIX\fR\&. This prefix is used in file names, function names, macro names, structure names, and the rest\&. When not specified in the configuration file, the default prefix is
99 \fB-h\fR, \fB--help\fR
106 Show the command\(cqs version\&.
121 Please report any bug or usability issue as a GitHub issue <https://github.com/efficios/barectf/issues>\&.
132 Project\(cqs website <http://barectf.org>
143 Continuous integration <http://ci.lttng.org/job/barectf>
154 Mailing list <http://lists.lttng.org>
155 for support and development:
156 \fBlttng-dev@lists.lttng.org\fR
157 (prefix the subject message with
169 IRC channel <irc://irc.oftc.net/lttng>:
174 is barectf\(cqs author and maintainer)
178 Copyright (c) 2014\-2016 Philippe Proulx <mailto:pproulx@efficios.com>\&.
180 barectf is distributed under the MIT License <https://github.com/efficios/barectf/blob/master/LICENSE>\&.
183 barectf was originally written by and is maintained by, as of this version, Philippe Proulx <mailto:pproulx@efficios.com>\&. Other, nice people have since contributed to the project\&.
185 barectf is supported by EfficiOS <http://www.efficios.com/>\&.