asn1c (Lev Walkin) extended with features required by MAP/TCAP
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Neels Hofmeyr 1ebab44b6f fix jenkins build: add contrib/jenkins.sh expected by jobs 5 years ago
asn1c unsigned integer of 32-bit widtth support for per 15 years ago
contrib fix jenkins build: add contrib/jenkins.sh expected by jobs 5 years ago
doc upgraded compatibility 15 years ago
examples necessary types added 15 years ago
libasn1compiler unsigned integer of 32-bit widtth support for per 15 years ago
libasn1fix with -> as 15 years ago
libasn1parser upgraded compatibility 15 years ago
libasn1print upgraded compatibility 15 years ago
skeletons per_support: Fix bit error in encoding process 12 years ago
tests unsigned integer of 32-bit widtth support for per 15 years ago
.gitignore build: Add a simple gitignore file... 12 years ago
AUTHORS Initial revision 19 years ago
BUGS BIT STRING identifiers is not a problem 18 years ago
COPYING copyright year 16 years ago
ChangeLog attribution 13 years ago
FAQ update: more documentation 17 years ago
INSTALL updated 18 years ago
MANIFEST Initial revision 19 years ago
Makefile.am CGI environment for online ASN.1 compilation 18 years ago
Makefile.in upgraded compatibility 15 years ago
NEWS build: Add dummy NEWS entry to make autoreconf --install --force succeed 12 years ago
README asn1c-quick.pdf 17 years ago
TODO PER encoding is mostly present 16 years ago
aclocal.m4 upgraded compatibility 15 years ago
asn1c.spec.in bit of description change 16 years ago
config.guess upgraded autotools 19 years ago
config.h.in do not include iberty if getopt is available by default. hurts CYGWIN 15 years ago
config.sub upgraded autotools 19 years ago
configure check for iberty before mkstemps: mingw fix 15 years ago
configure.in check for iberty before mkstemps: mingw fix 15 years ago
depcomp Initial revision 19 years ago
install-sh Initial revision 19 years ago
ltconfig Initial revision 19 years ago
ltmain.sh upgraded autotools 19 years ago
missing Initial revision 19 years ago
mkinstalldirs Initial revision 19 years ago
stamp-h.in Initial revision 19 years ago

README

WHAT TO READ?
=============

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
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.

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
specified:

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

<span class="escaped-code-point" data-escaped="[U+000C]"><span class="char"> </span></span>
MODEL OF OPERATION
==================

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
vlm@lionet.info