kc3-lang/libressl
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
168f4bc6 | 2024-02-04 19:16:14 | Windows: Improve the check for endianness when using Visual Studio. Visual studio does not define __BYTE_ORDER__ so all architectures were detected as LITTLE_ENDIAN since both __BYTE_ORDER__ and __ORDER_LITTLE_ENDIAN__ would evaluate to 0 and compare equal. This updates the checks to use CMakes detection of endianness, with a hard error, if this also fails. | |
|
d06a1136 | 2024-02-04 19:26:00 | Windows: Don't set -Wall when compiling with Visual Studio. As it enables a lot of spammed warnings that are not part of W4. This reduces the warnings a lot when compiling LibreSSL in CLion for me. | |
 |
c0951243 | 2024-01-14 14:46:52 | CI: limit scheduled runs to "libressl" org only | |
 |
84659877 | 2023-12-19 20:12:20 | Stop undefining X509_CERT_PAIR Pointed out in #910 | |
 |
759d2af4 | 2023-12-19 17:22:13 | readme: add windows badge | |
 |
b85c9dac | 2023-12-11 16:21:30 | cmake: auto-detect `strtonum` Notice that just like in autotools, this detection also doesn't take into account the targeted OS version. Meaning it detects `strtonum` even if targeting e.g. macOS older than release v11 Big Sur (which introduced this funcitions), if the SDK declares it. Wrong detection will either cause a binary broken on older macOS and/or trigger compiler warnings. Ref: https://github.com/libressl/portable/issues/928#issuecomment-1850178282 Ref: https://github.com/libressl/portable/issues/928#issuecomment-1850276298 Prerequisite: https://github.com/libressl/portable/issues/928#issuecomment-1850356408 | |
|
c4034613 | 2023-12-11 16:29:44 | delete broken link | |
|
3cb1ac9e | 2023-12-19 17:21:24 | ci: clean up windows workflow | |
|
819b6064 | 2023-12-11 16:21:00 | upgrade links in comments to HTTPS | |
|
9301c165 | 2023-12-20 02:23:16 | readme: fix grammatical error Co-authored-by: Theo Buehler <botovq@users.noreply.github.com> |