asn1c (Lev Walkin) extended with features required by MAP/TCAP
Go to file
Lev Walkin f3999547b2 comments and renaming 2004-10-21 11:21:43 +00:00
asn1c api change 2004-10-20 15:50:23 +00:00
doc ber_dec -> asn_dec 2004-10-20 15:48:55 +00:00
examples more skeletons 2004-10-20 15:49:29 +00:00
libasn1compiler XER support 2004-10-20 15:50:55 +00:00
libasn1fix things necessary for Sun Solaris 9 @ sparc 2004-10-20 15:40:04 +00:00
libasn1parser small fixes 2004-10-12 23:26:53 +00:00
libasn1print #CDATA is bogus 2004-10-15 06:01:54 +00:00
skeletons comments and renaming 2004-10-21 11:21:43 +00:00
tests XER support 2004-10-20 15:50:55 +00:00
AUTHORS Initial revision 2004-06-03 03:38:44 +00:00
BUGS just not tested 2004-10-20 15:48:09 +00:00
COPYING Initial revision 2004-06-03 03:38:44 +00:00
ChangeLog XER support and type renaming 2004-10-20 15:51:16 +00:00
FAQ typos 2004-10-03 10:54:05 +00:00
INSTALL recommendation to read the manual page 2004-09-06 08:07:55 +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 CGI environment for online ASN.1 compilation 2004-09-19 19:40:52 +00:00
NEWS Initial revision 2004-06-03 03:38:44 +00:00
README CGI environment for online ASN.1 compilation 2004-09-19 19:40:52 +00:00
TODO XER support removed from main targets: already in progress 2004-10-20 15:50:17 +00:00
aclocal.m4 upgraded autotools 2004-06-17 23:42:48 +00:00 order and typos fixed 2004-09-28 11:37:37 +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 -X for XML DTD 2004-10-13 09:13:56 +00:00 -X for XML DTD 2004-10-13 09:13:56 +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-usage.{pdf,html}.
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.


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