openssl/crypto/objects
Richard Levitte d5f9166bac Move e_os.h to include/internal
Including e_os.h with a path from a header file doesn't work well on
certain exotic platform.  It simply fails to build.

Since we don't seem to be able to stop ourselves, the better move is
to move e_os.h to an include directory that's part of the inclusion
path given to the compiler.

Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/17641)
2022-02-05 05:31:09 +01:00
..
build.info
o_names.c Move e_os.h to include/internal 2022-02-05 05:31:09 +01:00
obj_compat.h Fix copyrights 2022-02-03 13:56:38 +01:00
obj_dat.c object: use updated tsan lock detection capabilities 2022-01-13 21:46:34 +11:00
obj_dat.h Update troublesome copyright years of auto-generated files to 2022 2022-01-03 13:41:16 +01:00
obj_dat.pl
obj_err.c Update copyright year 2021-06-17 13:24:59 +01:00
obj_lib.c
obj_local.h
obj_mac.num Add OID for RPKI id-ct-ASPA 2021-11-11 13:02:29 +01:00
obj_xref.c Permit no/empty digest in core_obj_add_sigid 2021-10-22 16:26:46 +02:00
obj_xref.h Fix copyright year issues 2022-01-06 09:27:02 +01:00
obj_xref.txt
objects.pl
objects.txt Add OID for RPKI id-ct-ASPA 2021-11-11 13:02:29 +01:00
objxref.pl
README.md

objects.txt syntax

To cover all the naming hacks that were previously in objects.h needed some kind of hacks in objects.txt.

The basic syntax for adding an object is as follows:

    1 2 3 4         : shortName     : Long Name

            If Long Name contains only word characters and hyphen-minus
            (0x2D) or full stop (0x2E) then Long Name is used as basis
            for the base name in C. Otherwise, the shortName is used.

            The base name (let's call it 'base') will then be used to
            create the C macros SN_base, LN_base, NID_base and OBJ_base.

            Note that if the base name contains spaces, dashes or periods,
            those will be converted to underscore.

Then there are some extra commands:

    !Alias foo 1 2 3 4

            This just makes a name foo for an OID.  The C macro
            OBJ_foo will be created as a result.

    !Cname foo

            This makes sure that the name foo will be used as base name
            in C.

    !module foo
    1 2 3 4         : shortName     : Long Name
    !global

            The !module command was meant to define a kind of modularity.
            What it does is to make sure the module name is prepended
            to the base name.  !global turns this off.  This construction
            is not recursive.

Lines starting with # are treated as comments, as well as any line starting with ! and not matching the commands above.