asn1c (Lev Walkin) extended with features required by MAP/TCAP
Go to file
Lev Walkin 16835b66d4 better constraint failure reporting 2004-08-22 13:47:59 +00:00
asn1c better dependency tracking 2004-08-22 03:08:23 +00:00
doc version bump-up 2004-08-11 05:35:51 +00:00
examples version bump-up 2004-08-11 05:35:51 +00:00
libasn1compiler better constraint failure reporting 2004-08-22 13:47:59 +00:00
libasn1fix refactoring 2004-08-22 03:10:23 +00:00
libasn1parser COMPONENTS OF support and other enhancements 2004-08-22 03:19:54 +00:00
libasn1print pretty-printing COMPONENTS OF 2004-08-22 03:08:51 +00:00
skeletons better constraint failure reporting 2004-08-22 13:47:59 +00:00
tests better constraint failure reporting 2004-08-22 13:47:59 +00:00
AUTHORS Initial revision 2004-06-03 03:38:44 +00:00
BUGS Initial revision 2004-06-03 03:38:44 +00:00
COPYING Initial revision 2004-06-03 03:38:44 +00:00
ChangeLog better constraint failure reporting 2004-08-22 13:47:59 +00:00
FAQ new file 2004-08-20 13:38:07 +00:00
INSTALL Initial revision 2004-06-03 03:38:44 +00:00
MANIFEST Initial revision 2004-06-03 03:38:44 +00:00 order changed 2004-08-18 04:45:17 +00:00 last touches 2004-08-18 05:43:55 +00:00
NEWS Initial revision 2004-06-03 03:38:44 +00:00
README Initial revision 2004-06-03 03:38:44 +00:00
TODO reprioritizing 2004-08-22 03:20:15 +00:00
aclocal.m4 upgraded autotools 2004-06-17 23:42:48 +00:00
config.guess upgraded autotools 2004-06-17 23:42:48 +00:00 Initial revision 2004-06-03 03:38:44 +00:00
config.sub upgraded autotools 2004-06-17 23:42:48 +00:00
configure versioning 2004-08-19 13:35:01 +00:00 versioning 2004-08-19 13:35:01 +00:00
depcomp Initial revision 2004-06-03 03:38:44 +00:00
install-sh Initial revision 2004-06-03 03:38:44 +00:00
ltconfig Initial revision 2004-06-03 03:38:44 +00:00 upgraded autotools 2004-06-17 23:42:48 +00:00
missing Initial revision 2004-06-03 03:38:44 +00:00
mkinstalldirs Initial revision 2004-06-03 03:38:44 +00:00 Initial revision 2004-06-03 03:38:44 +00:00


This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.


For quick installation tips read INSTALL.

For more complete documentation on this compiler and on using the
results of compilation please look into ./doc directory.

An excellent book on ASN.1 is written by Olivier Dubuisson:
"ASN.1 Communication between heterogeneous systems", ISBN:0-12-6333361-0.


After building [and installing] the compiler (see INSTALL), you may use
the asn1c command to compile the ASN.1 specification:

	asn1c <spec.asn1>

If several specifications contain interdependencies, all of them must be

	asn1c <spec1.asn1> <spec2.asn1> ...

The ./examples directory contains several ASN.1 modules and a script to
extract ASN.1 modules from RFC documents. To compile X.509 PKI module:

	./asn1c/asn1c -P ./examples/*PKIX*93*.asn1

In this example, -P option is used to instruct the compiler to print the
compiled text on the standard output instead of creating multiple .c
and .h files for every ASN.1 type found inside the specified files.
This is useful for debugging and tests automation.

The compiler -E and -EF options are used for testing the parser and
the semantic fixer, respectively. These options will instruct the compiler
to dump out the parsed (and fixed) ASN.1 specification as it was
"understood" by the compiler. It might be useful for checking
whether a particular syntactic construction is properly supported
by the compiler.

	asn1c -EF <spec-to-test.asn1>


The asn1c compiler works by processing the ASN.1 module specification
in several stages:
1. In the first stage, the ASN.1 file is parsed.
	(Parsing produces an ASN.1 syntax tree for the subsequent levels.)
2. In the second stage, the syntax tree is "fixed".
	(Fixing is done by checking the tree for semantic errors
	 and by transforming the tree into the canonical representation.)
3. In the third stage, the syntax tree is compiled into the target language.

There are several command-line options reserved for printing the results
after each stage of operation:

	<parser> => print					(-E)
	<parser> => <fixer> => print				(-E -F)
	<parser> => <fixer> => <compiler> => print		(-P)
	<parser> => <fixer> => <compiler> => save-compiled	[default]

Lev Walkin