]> git.saurik.com Git - apple/security.git/blob - SecuritySNACCRuntime/doc/mkchdr.1
Security-54.1.tar.gz
[apple/security.git] / SecuritySNACCRuntime / doc / mkchdr.1
1 .\" Copyright (c) 1993 by Mike Sample and UBC
2 .\" See section COPYING for conditions for redistribution
3 .\" $Header: /cvs/Darwin/Security/SecuritySNACCRuntime/doc/mkchdr.1,v 1.1.1.1 2001/05/18 23:14:10 mb Exp $
4 .\" $Log: mkchdr.1,v $
5 .\" Revision 1.1.1.1 2001/05/18 23:14:10 mb
6 .\" Move from private repository to open source repository
7 .\"
8 .\" Revision 1.1.1.1 1999/03/16 18:05:53 aram
9 .\" Originals from SMIME Free Library.
10 .\"
11 .\" Revision 1.2 1997/01/01 22:47:18 rj
12 .\" first check-in
13 .\"
14 .TH MKCHDR 1 "11 July 1993"
15 .SH NAME
16 mkchdr \- creates a C header file from a type table
17 .SH SYNOPSIS
18 .nf
19 mkchdr <tbl-file> [output-file]
20 .SH DESCRIPTION
21 mkchdr will generate a C header file from the given type table. The C
22 data structures will be written to the given output file. If an
23 output file is not given, the C header is written to stdout.
24
25 The generated C data structure is the value representation that table
26 driven encoder expects (and decoder returns) for the type definitions
27 in the given type table. The table driven encoder and decoder, etc.
28 routines do not use the generated header - they treat the data in a
29 generic way. The generated header file simply saves you the hassle of
30 dealing with ASN.1 values in the same generic way. Instead you get
31 properly named structs and field names. You do not need to use mkchdr
32 to use the table driven encoders etc. but it is recommended.
33 .PP
34 .\" there is a tab between the file name and the description
35 .SH FILES
36 .PD 0
37 .TP 28
38 .B snacc/tbl-tools/mkchdr/
39 Source code for the mkchdr program
40 .PD
41 .SH BUGS
42 There is no means of customizing the generated data structure.
43 .SH COPYING
44 Copyright (c) 1993 Mike Sample and the University of British Columbia
45 .PP
46 Permission is granted to make and distribute verbatim copies of
47 this manual provided the copyright notice and this permission notice
48 are preserved on all copies.
49 .PP
50 Permission is granted to copy and distribute modified versions of this
51 manual under the conditions for verbatim copying, provided that the
52 entire resulting derived work is distributed under the terms of a
53 permission notice identical to this one.
54 .PP
55 .SH AUTHOR
56 Mike Sample <msample@cs.ubc.ca>, University of British Columbia
57 .SH ACKNOWLEDGEMENTS
58 This work was made possible by grants from the Canadian Institute for
59 Telecommunications Research (CITR) and Natural Sciences and
60 Engineering Research Council of Canada (NSERC).