1 .TH compiler 1 "October 2014" "Ericsson Telecom AB" "TTCN-3 Tools"
3 compiler \- TTCN-3 and ASN.1 to C++ translator
6 .RB "[\| " \-abcdEfgijlLMpqrRsStuwxXyY " \|]"
8 .IR " verb_level" " \|]"
16 .IR " top_level_pdu" " \|] ..."
20 .IR "none|type" " \|] "
25 [\| \- module.ttcn ... module.asn ... \|]
34 .B compiler \-\-ttcn2json
35 .RB "[\| " \-jf " \|]"
44 This manual page is a quick reference for the TTCN-3 and ASN.1 to C++ (or JSON schema)
45 compiler of the TTCN-3 Test Executor. It only summarizes the meaning of
46 all command line options. For more details please consult the
47 .B Programmer's Technical Reference for TITAN TTCN-3 Test Executor.
49 The following options are supported (in alphabetical order):
52 Forces the interpretation of
56 It is useful when automatic module type detection fails
57 due to some strange language constructs. The option takes exactly one file
58 name as argument. The option must be repeated when used with multiple files.
68 Disables the generation of
70 encoder/decoder routines for all ASN.1 types.
73 Allows the selected field in a union value to be unbound, when setting module
74 parameters (legacy behavior). A warning is displayed whenever a union value
75 receives an unbound selected field and when a union with an unbound selected field
86 fields with DEFAULT values as
91 Instructs the variant attribute parser to display warnings instead of errors
92 for unrecognized/erroneous attributes.
95 Forces the compiler to
97 the output files even if they exist or are unchanged.
100 The compiler error/warning messages will contain only the starting
101 line number and column, in a format compatible with th GNU compiler (gcc).
103 takes precedence over
105 if both are specified.
108 The compiler error/warning messages
109 will contain only the
111 the column numbers will remain hidden. This option provides backward
112 compatibility with the error message format of earlier versions.
115 Disables JSON encoder/decoder functions.
118 Enables selective code coverage.
121 Instructs the compiler to generate source file and line information (i.e.
123 directives) into the output C++ code so that the C++ compiler error
124 messages refer back to the lines of original TTCN-3 input module.
128 and will be removed in future versions as the
129 compiler does not generate erroneous C++ code because of the full
133 Instructs the compiler to add source file and line
137 information into the generated code to be included in the
141 This option is only a prerequisite for logging the source code information.
146 have also to be set appropriately in section
148 of the run-time configuration file.
150 Usage of this option a bit enlarges the size of the generated code and slightly
151 reduces execution speed. This flag is not recommended when the TTCN-3 test
152 suite is used for load generation.
155 Allows the use of the value
157 in template lists and complemented template lists (legacy behavior).
158 If set, an omitted field will match a template list, if the value
160 appears in the list, and it will match a complemented template list, if
162 is not in the list (the
164 attribute can still be used for matching omitted fields). This also affects the
168 template restriction accordingly.
171 The output files (including Test Port skeletons) will be placed into
172 the directory specified by
174 The current working directory is the default otherwise.
177 Instructs the compiler only to
179 the given TTCN-3 and ASN.1 modules. This will detect only the syntax errors
180 because semantic checkings are
182 performed. The presence of all imported modules is not necessary thus it is
183 allowed (and recommended) to parse the modules one-by-one.
185 All options that influence the code generation are silently ignored when used
190 This option includes complete syntax checks for TTCN-3 modules, but in ASN.1
191 there are some special constructs (e.g. the user-defined syntaxes) that cannot
192 be even parsed without semantic analysis. So there is no guarantee that an ASN.1
193 module is free of syntax errors if it was analyzed with compiler using the
197 .BI \-P " top_level_pdu" ...
198 Defines a top-level pdu.
200 must have the following format:
201 .I modulename.identifier.
202 If this switch is used, then only the defined top-level PDU(s) and the
203 referenced assignments are checked and included in code generation, the
204 other ASN.1 assignments are skipped.
208 mode. Equivalent with
218 Disables the generation of
220 encoder/decoder routines for all TTCN-3 types.
223 Use function test runtime (TITAN_RUNTIME_2). The compiler will generate source
224 code for use with function test runtime.
227 Instructs the compiler to parse the given TTCN-3 and ASN.1 modules and perform
231 to generate C++ output. The list of given modules shall be complete so it is
232 not allowed to import from a module that is not in the list. All options that
233 influence the code generation are silently ignored when used together with
243 skeleton header and source files for all port types that can be found in
244 TTCN-3 modules. Existing Test Port files will not be overwritten unless the
249 Forces the interpretation of
257 Forces the compiler to do
258 .I duplicate underscore
259 characters in all output file names. This option turns on the
260 compatibility mode with versions 1.1 or earlier.
263 Selects code splitting mode for the generated C++ code.
268 and license key information and exits.
270 .BI \-V " verb_level"
271 Sets the verbosity bit-mask directly to
275 is a decimal value between 0 and 65535).
284 "NOT SUPPORTED" messages.
295 The debug-bits act like a 3-bits-length number, so the debug level has
296 a value between 0 and 7. It is useful in case of abnormal program termination.
304 messages. Equivalent with
308 Disables the generation of
310 encoder/decoder routines for all TTCN-3 types.
315 encoder/decoder functions
323 Enforces legacy behaviour of the "out" function parameters (see refguide).
326 Enables profiling and code coverage in the selected TTCN-3 files. The
328 argument contains a list of TTCN-3 files separated by new lines. Each TTCN-3 file must be among the compiler's TTCN-3 file arguments.
331 The single dash character as command line argument controls the
332 .I selective code generation
334 After the list of all TTCN-3 and ASN.1 modules a subset of these files can
335 be given separated by a dash. This option instructs the compiler to parse all
336 modules, perform the semantic analysis on the entire module hierarchy, but
339 for those modules that are listed after the dash again.
341 It is not allowed to specify a file name after the dash that was not present
342 in the list before the dash. If the single dash is not present in the command
343 line the compiler will generate code for
348 Generates a JSON schema from the types defined in the specified TTCN-3 and ASN.1 modules.
349 Must always be the first compiler option. From the previously listed options only
353 can be used, instead the JSON schema generator has options of its own:
356 Only types that have JSON coding enabled are included in the schema.
359 The schema only validates types that have a JSON encoding or decoding method declared.
362 The single dash character as command line argument specifies the name of the generated
363 JSON schema file. If it is not present, then the schema file name is generated from
364 the name of the first input file (by replacing its suffix with
368 to the end of the file).
370 The compiler exits with a status of zero when no errors were encountered
371 during its operation. A status of one will be returned if syntax or
372 semantic errors were detected in the input modules.
373 .SH ENVIRONMENT VARIABLES
377 The installation directory where the uncompressed binary package of
378 TTCN-3 Test Executor can be found.
382 It shall point to the
386 to its directory) that contains the personalized license key for the
387 current user or host.
389 The compiler does not support all constructs of TTCN-3 Core Language and ASN.1.
390 It reports an error when encountering an unsupported language element.
391 The detailed list of deficiencies and language extensions can be found in the
392 referenced documentation.
394 For trouble reporting use the tool
396 For TR writers guide please visit the web page:
397 .I http://ttcn.ericsson.se.
401 Ericsson document 2/198 17-CRL 113 200 Uen:
402 .B Programmer's Technical Reference for TITAN TTCN-3 Test Executor
405 ETSI Standard ES 201-873-1:
406 .B Testing and Test Control Notation: TTCN-3 Core Language
409 ITU-T Recommendations X.680-683:
410 .B Abstract Syntax Notation One (ASN.1)
412 This manpage is written by Janos Zoltan Szabo, Ericsson Telecom AB
414 Copyright (c) 2000-2016 Ericsson Telecom AB
416 All rights reserved. This program and the accompanying materials
417 are made available under the terms of the Eclipse Public License v1.0
418 which accompanies this distribution, and is available at
420 http://www.eclipse.org/legal/epl-v10.html