mavros \- ASN.1 compiler


mavros input_filename [ \-name module ][ \-d file_names ][ \-s module_names ][ \-i file_names ][ \-cod ] [ \-a ] [ \-c ] [ \-w ] [ \-ser ] [ \-inc ] [ \-mak ] [ \-m module ][ -all] [ \-u ] [ \-um ] [ \-ut ] [ \-bs block-size ][ \-p ] [ \-x debuglevel ][ \-XOM ] [ \-session ] [ \-nolinenum ] [ \-extent93 ] [ \-af_anydef ] [ \-windows ] [ \-BS2000 ] [ \-constants ] [ \-compat ] [ \-notextformat ] [ \-nocerstring ]


The code generator MAVROS is the second pass of the "mavros" compiler. It translates the description of the data types, operations and errors, whose syntax is given in annotated ASN.1 in the file named input_filename into a set of C procedures for encoding and decoding the described data types.

MAVROS will produce:

according to various parametrizations, specified by command line arguments.


Mavros has several options, which describe the source file, the type of routine that should be generated and the way these routines should be grouped into files. A set of miscellaneous arguments can be used for introducing debugging information, and also for various code parametrizations. MAVROS takes its informations from a source file in "MVR" format. The user should also supply if necessary the list of auxiliary "header" and "source" files, using the following arguments: MAVROS can generate several types of coding and decoding procedures (see the corresponding manual pages). A set of parameters can be used to specify which type should be generated: By default, MAVROS creates one file per coding or decoding routine. This behaviour can be parametrize by the following set of options: When the default mode is used, the name of the file will be constructed by appending the hexadecimal type number and the coding mode identifier to the module name, e.g. module_c1g.c. These names will always stay within a 14 characters limit. The particular names which have been generated will be listed in the "make" file of the module. The list of files to be compiled will be named "CFILES", the list of object file to be compiled will be named "OFILES". These list may well become very long for large specifications, which may be unacceptable for some systems. One particular option can be used in this case: Several options can be used in order to debug a ".mvr" specification and the corresponding source and header files: Various miscellaneous arguments can be used to accomodate special usages of MAVROS:


mavcod (9x),
mavros-output (9x),
C. Huitema, "General Presentation of the MAVROS Compiler" ,INRIA, 1990


The diagnostics produced by MAVROS are intended to be self explanatory.


Please report bugs to the authors..