| commit | b43722d878616bed05b4cb8a49d19c5f02bd58ab | [log] [tgz] |
|---|---|---|
| author | Oliver Smith <osmith@sysmocom.de> | Wed Dec 21 13:44:17 2022 +0100 |
| committer | Oliver Smith <osmith@sysmocom.de> | Wed Dec 21 14:17:20 2022 +0100 |
| tree | 8affdb07ee0ae51efdc4de11aec1b317f5af2ea8 | |
| parent | 4234af335f998dde68da41381d4630fe9231ec34 [diff] |
contrib/jenkins.sh: update for aper-prefix tree Add the missing 'autoreconf -fi', and disable 'make check' as checks on this branch are failing with: fatal: making test-suite.log: failed to create ../tests/00-empty-OK.asn1.trs I spent some time looking into it and don't see why it is doing that, and it doesn't seem worth investing more time right now as we are not actively developing on asn1c currently (and if we were it probably made more sense to try to rebase on the upstream version / try to upstream our additions?) so just disable 'make check'. To explain what "this branch" is: * We used to have a master branch (now old-master), which was based on 2010 upstream code of asn1c with aper related patches on top. It had the contrib/jenkins.sh script and 'make check' was passing. * In practice we've been using the "aper-prefix" branch for the past years (to generate files for osmo-iuh.git), which was based on 2015 code from asn1c with the aper related patches and a patch to add ASN1C_PREFIX to avoid clashing names of generated files on top. There, no contrib/jenkins.sh file was present and 'make check' was failing. So this new branch is the same as "aper-prefix", but with the contrib/jenkins.sh file and now this patch to make it pass. Related: OS#2435 Related: upstream development: https://github.com/vlm/asn1c Change-Id: I79a398cba75339c308f56c2e44ea99b3776be164
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.
The comprehensive documentation on this compiler is in asn1c-usage.pdf.
If you are building the compiler from the sources, the PDFs reside in the ./doc directory. Normally the file is installed together with the README.md 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.
(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
The asn1c compiler works by processing the ASN.1 module specifications in several stages:
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