summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorDr. David von Oheimb <David.von.Oheimb@siemens.com>2020-06-10 14:15:28 +0200
committerDr. David von Oheimb <David.von.Oheimb@siemens.com>2020-07-05 11:29:43 +0200
commit036cbb6bbf30955abdcffaf6e52cd926d8d8ee75 (patch)
tree1929b9d33c7041858cbbed980f8c981d8eb77c3c /HACKING
parent915e7e75a49343ff5ddd23a54219eb32f57aa01c (diff)
downloadopenssl-new-036cbb6bbf30955abdcffaf6e52cd926d8d8ee75.tar.gz
Rename NOTES*, README*, VERSION, HACKING, LICENSE to .md or .txt
Reviewed-by: Tim Hudson <tjh@openssl.org> (Merged from https://github.com/openssl/openssl/pull/12109)
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING26
1 files changed, 0 insertions, 26 deletions
diff --git a/HACKING b/HACKING
deleted file mode 100644
index abf199f541..0000000000
--- a/HACKING
+++ /dev/null
@@ -1,26 +0,0 @@
- MODIFYING OPENSSL SOURCE
- ------------------------
- This document describes the way to add custom modifications to OpenSSL sources.
-
- If you are adding new public functions to the custom library build, you need to
- either add a prototype in one of the existing OpenSSL header files;
- or provide a new header file and edit Configurations/unix-Makefile.tmpl to pick up that file.
-
- After that perform the following steps:
-
- ./Configure -Werror --strict-warnings [your-options]
- make update
- make
- make test
-
- "make update" ensures that your functions declarations are added to util/libcrypto.num or util/libssl.num
- If you plan to submit the changes you made to OpenSSL (see CONTRIBUTING), it's worth running:
-
- make doc-nits
-
- after running "make update" to ensure that documentation has correct format.
-
- "make update" also generates files related to OIDs (in the crypto/objects/ folder) and errors.
- If a merge error occurs in one of these generated files then the generated files need to be removed
- and regenerated using "make update".
- To aid in this process the generated files can be committed separately so they can be removed easily.