1ecppc(1) Tntnet users guide ecppc(1)
2
6 ecppc - compiler for ecpp(7)
7
10 ecppc [-bhszvtM] [-s-] [-o filename] [-n name] [-m mimetype] [--mime‐
11 types filename] [-I dir] [-l log-category] filename
12 ecppc -bb filename ...
15 ecppc [OPTION]
18
21 ecppc is the compiler for the ecpp-language. ecpp is a template lan‐
22 guage, which lets the user embed C++-code into HTML for use in
23 tntnet(8). ecppc generates a C++-class from a ecpp template. It can
24 also compile binary data into a C++-class, which makes it possible to
25 integrate them in a tntnet application.
26
29 -b
30 This enables binary-mode. Ecppc does not look for ecpp-tags, but cre‐
31 ates a
32 class, which just copies the data
33 -bb
36 This enables multi-binary-mode. Every binary-file has some overhead,
37 when
38 packed into a tntnet-application. This overhead can be quite signifi‐
39 cant, when
40 binary-files are small, like small icons in a web application. To
41 reduce this
42 overhead, multiple binaries can be packed into a single class, which
43 removes
44 the per-binary overhead completely.
45 When the component is called, it uses the path-info-parameter
48 (request.getPathInfo()) from the request, to decide, which binary to
49 send. If
50 no filename matches the path-info, processing is declined. The bina‐
51 ries need
52 not be of same mime-type, since the mime-type is looked automatically
53 from the
54 mime-database by file- extension of the source-file.
55 -i filename
58 In multi binary mode (option -bb) filenames can be read from the file
59 specified with this option. This can be useful when the command line
60 gets too
61 long or just for convenience.
62 -I dir
65 Search include-files in directory. This option can be passed multiple
66 times.
67 All specified directories are searched in turn for include-files.
68 -l log-category
71 Set log category. Default is component.componentname.
72 -L
75 Disable generation of #line-directives
76 -m mimetype
79 Set mimetype of output. This is the mimetype, sent by the component
80 to the
81 browser in the Content-Type- header. Without this parameter the mime‐
82 type is
83 looked up from the mime-database of your system using the file-exten‐
84 sion of
85 the source-file.
86 --mimetypes file
89 Read mimetypes from file (default: /etc/mime.types).
90 -M
93 This disables normal processing and prints just the ecpp-dependencies
94 from
95 this component. The output can be included into a Makefile.
96 Ecpp-dependencies
97 are introduces by the <%include>-tag.
98 -C, --cmake
101 Prints ecpp dependencies in a syntax, which cmake understands.
102 -n name
105 Set the name of the component. Normally this is derived from the
106 source-file-name by removing the path and .ecpp-extension.
107 -o filename
110 Write the generated file to the specified file instead of deriving
111 the
112 filename from the source-file-name. The outputfilename is normally
113 the
114 source-file where the extension is replaced by .cpp.
115 -p
118 Keep path name when deriving name of component from input file name.
119 -s
122 Generate singleton. Normally ecppc decides automatically, if the tem‐
123 plate is
124 suitable for a singleton. This option force ecppc to generate a sin‐
125 gleton.
126 -s-
129 Do not generate a singleton.
130 -v
133 Enable verbose mode. This prints additional information about the
134 processing
135 on the standard-output.
136 -z
139 Compress the data in the component. Compressed data is automatically
140 decopressed on first use. This reduces the code-size, but slightly
141 slows down
142 the first call of the component.
143 -h, --help
146 display this information
147 -V, --version
150 display program version
151
154 This manual page was written by Tommi Mäkitalo ⟨tommi@tntnet.org⟩.
155
158 tntnet(8), ecpp(7)
159Tntnet 2006-07-23 ecppc(1)