The Open Cryptography Kit for C to which this document refers is based on the C language and is usable by products that are based on C or C++.
For a debug build on any platform specify CONFIG=debug as an argument to make.
make -k -C icc OPSYS=AMD64_LINUX create_all
make -k -C icc OPSYS=AMD64_LINUX allmake -k -C icc OPSYS=LINUX create_all
make -k -C icc OPSYS=LINUX allmake -k -C icc OPSYS=WIN64_VS2022 create_all
make -k -C icc OPSYS=WIN64_VS2022 allThis build is not constrained to MS VS 2022 but is tested on that platform.
Visual studio build tools are required, including mfc.
The supported make is windows gnumake 3.81. Also required is NASM, common unix utilities for windows (ls, sh, mv, rm, patch, etc), strawberry perl, and openjdk.
Tested unix utilities are provided by msys2, or those packaged with the windows git installer.
The tested openjdk is the Microsoft Build of OpenJDK 17.
NASM should be added to the windows PATH environment variable.
Run the appropriate vcvars.bat file in a cmd.exe or otherwise use a development console before running make.
Note: Windows utilities which use a Unix style PATH such as the gnumake available in msys2 are not supported.
Note: Cygwin is not supported.
The following contribution guidelines should be followed:
-
View this projects LICENSE file. Be sure terms and conditions are acceptable.
-
A pull request should be sent for review only after the github action associated with this repository is automatically executed when a pull request is created.
-
AI-Assisted Contributions: We welcome the use of Bob (the only approved AI tool at this time) throughout the codebase. All Bob-assisted contributions must be properly validated. See our comprehensive AI Contributions Guide for detailed requirements including:
- APPROVED TOOL: Only Bob is permitted - other AI tools are not allowed
- Legal compliance and validation procedures
- Security considerations for cryptographic code
- Best practices for AI-assisted development
- Code review process for Bob-assisted contributions