asn1c (Lev Walkin) extended with features required by MAP/TCAP
Go to file
Lev Walkin c5a5d22cd5 some fixes 2007-06-23 17:35:56 +00:00
asn1c further svnization 2007-05-23 10:15:39 +00:00
doc *** empty log message *** 2006-09-19 04:59:55 +00:00
examples a file for testing TAP3-11 decoding 2007-06-05 08:07:39 +00:00
libasn1compiler some fixes 2007-06-23 17:35:56 +00:00
libasn1fix some fixes 2007-06-23 17:35:56 +00:00
libasn1parser bit string value constraints parsing 2006-10-27 05:37:39 +00:00
libasn1print dtd for bit string 2006-11-21 10:39:52 +00:00
skeletons some fixes 2007-06-23 17:35:56 +00:00
tests BMPString and UniversalString support 2006-11-24 11:20:27 +00:00
AUTHORS Initial revision 2004-06-03 03:38:44 +00:00
BUGS BIT STRING identifiers is not a problem 2005-02-28 15:35:27 +00:00
COPYING happy new year 2006-03-18 07:23:52 +00:00
ChangeLog PER support for BMPString and UniversalString 2006-11-24 11:27:37 +00:00
FAQ update: more documentation 2005-12-22 21:36:47 +00:00
INSTALL updated 2005-02-25 12:27:04 +00:00
MANIFEST Initial revision 2004-06-03 03:38:44 +00:00 CGI environment for online ASN.1 compilation 2004-09-19 19:40:52 +00:00 MEGACO (Media Gateway Control) protocol decoder 2006-09-09 04:49:45 +00:00
NEWS Initial revision 2004-06-03 03:38:44 +00:00
README asn1c-quick.pdf 2005-11-21 09:17:43 +00:00
TODO PER encoding is mostly present 2006-09-19 06:12:11 +00:00
aclocal.m4 automake-1.9 2006-08-18 01:54:27 +00:00 2006-09-19 01:07:24 +00:00
config.guess upgraded autotools 2004-06-17 23:42:48 +00:00 portability fixes 2005-02-25 14:20:30 +00:00
config.sub upgraded autotools 2004-06-17 23:42:48 +00:00
configure 0.9.22 2006-10-09 12:29:34 +00:00 0.9.22 2006-10-09 12:29:34 +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.


If you haven't installed the asn1c yet, read the INSTALL file for
a short installation guide.

For the list of asn1c command line options, see `asn1c -h` or `man asn1c`.

For more complete documentation on this compiler and on using the
results of compilation phase, please look into asn1c-quick.pdf and
If you are building the compiler from the sources, these documents reside
in the ./doc directory, otherwise they lie nearby the README file you're
reading right now.

Please also read the FAQ file.

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

QUICK START (also check out asn1c-quick.pdf)

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

	asn1c <module.asn1>			# Compile module

If several specifications contain interdependencies, all of them must be

	asn1c <module1.asn1> <module2.asn1> ...	# Compile interdependent modules

If you are building the asn1c from the sources, the ./examples directory
contains several ASN.1 modules and a script to extract the ASN.1 modules
from RFC documents. Refer to the README file in that directory.
To compile the X.509 PKI module:

	./asn1c/asn1c -P ./examples/rfc3280-*.asn1	# Compile-n-print

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 ASN.1 modules.
This is useful for debugging and test 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 <module-to-test.asn1>		# Check semantic validity


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 a process of checking the tree for semantic errors,
	 accompanied by the tree transformation into the canonical form)
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