Yes, that would be a good idea. Although it does not prevent merge conflicts, at least the ordinals
don't have to be renumbered every time. (That's the way we solved the problem in our company.)
On 27.11.18 15:58, Viktor Dukhovni wrote:
On Nov 27, 2018, at 7:38 AM, Dr. Matthias St. Pierre <Matthias.St.Pierre@xxxxxxxxx> wrote:
Short version: Just do 'make update' and the numbers will be added automagically.
Long version: There is a script, 'util/mkdef.pl', which gets invoked by 'make update'. It scans the header files
for new APIs an updates the .num files (libcrypto.num/libeay.num and libssl.num) accordingly. For windows,
it also updates the module definition files (*.def).
It might be prudent for the OP to assign a high value that OpenSSL
will not likely ever reach. Start at 32767 and count down for site-local
ordinals?
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
