6cc903880d
The perl script is a little nuts. obj_dat.pl actually parses the header file that objects.pl emits to figure out what all the objects are. Replace it all with a single Go script. BUG=16 Change-Id: Ib1492e22dbe4cf9cf84db7648612b156bcec8e63 Reviewed-on: https://boringssl-review.googlesource.com/12963 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| obj_dat.h | ||
| obj_mac.num | ||
| obj_test.cc | ||
| obj_xref.c | ||
| obj.c | ||
| objects.go | ||
| objects.txt | ||
| README | ||
The files nid.h, obj_mac.num, and obj_dat.h are generated from objects.txt and
obj_mac.num. To regenerate them, run:
go run objects.go
objects.txt contains the list of all built-in OIDs. It is processed by
objects.go to output obj_mac.num, obj_dat.h, and nid.h.
obj_mac.num is the list of NID values for each OID. This is an input/output
file so NID values are stable across regenerations.
nid.h is the header which defines macros for all the built-in OIDs in C.
obj_dat.h contains the ASN1_OBJECTs corresponding to built-in OIDs themselves
along with lookup tables for search by short name, OID, etc.