1ecppc(1) Tntnet users guide ecppc(1)
2
6 ecppc - compiler for ecpp(7)
7
9 ecppc [-bhszvtM] [-s-] [-o filename] [-n name] [-m mimetype] [--mime‐
10 types filename] [-I dir] [-l log-category] filename
11 ecppc -bb filename ...
13
15 ecppc is the compiler for the ecpp-language. ecpp is a template lan‐
16 guage, which lets the user embed C++-code into HTML for use in tnt‐
17 net(8). ecppc generates a C++-class from a ecpp template. It can also
18 compile binary data into a C++-class, which makes it possible to inte‐
19 grate them in a tntnet application.
20
22 -b This enables binary-mode. Ecppc does not look for ecpp-tags, but
23 creates a class, which just copies the data
24 -bb This enables multi-binary-mode. Every binary-file has some over‐
26 head, when packed into a tntnet-application. This overhead can
27 be quite significant, when binary-files are small, like small
28 icons in a web application. To reduce this overhead, multiple
29 binaries can be packed into a single class, which removes the
30 per-binary overhead completely.
31 When the component is called, it uses the path-info-parameter
33 (request.getPathInfo()) from the request, to decide, which
34 binary to send. If no filename matches the path-info, processing
35 is declined. The binaries need not be of same mime-type, since
36 the mime-type is looked automatically from the mime-database by
37 file- extension of the source-file.
38 -i filename
40 In multi binary mode (option -bb) filenames can be read from the
41 file specified with this option. This can be useful when the
42 command line gets too long or just for convenience.
43 -I dir Search include-files in directory. This option can be passed
45 multiple times. All specified directories are searched in turn
46 for include-files.
47 -l log-category
49 Set log category. Default is component.componentname.
50 -L Disable generation of #line-directives
52 -m mimetype
54 Set mimetype of output. This is the mimetype, sent by the compo‐
55 nent to the browser in the Content-Type- header. Without this
56 parameter the mimetype is looked up from the mime-database of
57 your system using the file-extension of the source-file.
58 --mimetypes file
60 Read mimetypes from file (default: /etc/mime.types).
61 -M This disables normal processing and prints just the ecpp-depen‐
63 dencies from this component. The output can be included into a
64 Makefile. Ecpp-dependencies are introduces by the
65 <%include>-tag.
66 -n name
68 Set the name of the component. Normally this is derived from the
69 source-file-name by removing the path and .ecpp-extension.
70 -o filename
72 Write the generated file to the specified file instead of deriv‐
73 ing the filename from the source-file-name. The outputfilename
74 is normally the source-file where the extension is replaced by
75 .cpp.
76 -p Keep path name when deriving name of component from input file
78 name.
79 -s Generate singleton. Normally ecppc decides automatically, if the
81 template is suitable for a singleton. This option force ecppc
82 to generate a singleton.
83 -s- Do not generate a singleton.
85 -v Enable verbose mode. This prints additional information about
87 the processing on the standard-output.
88 -z Compress the data in the component. Compressed data is automati‐
90 cally decopressed on first use. This reduces the code-size, but
91 slightly slows down the first call of the component.
92
94 This manual page was written by Tommi Mäkitalo ⟨tommi@tntnet.org⟩.
95
97 tntnet(1), ecpp(7), ecppl(1), ecppll(1)
98Tntnet 2006-07-23 ecppc(1)