You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-21Lines changed: 17 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,20 @@ This project regularly builds the latest available vcpkg version of the followin
33
33
*`com.ensody.nativebuilds:zstd`: headers and static library
34
34
35
35
The artifacts are published to Maven Central, so they can be easily consumed by Gradle and Kotlin Multiplatform projects.
36
+
A Gradle plugin is also provided to simplify the integration of the header files.
37
+
38
+
Apart from being easier to integrate, this project helps you stay up to date.
39
+
The NativeBuilds automatically publish new versions to Maven Central.
40
+
Tools like Dependabot can notify you of version updates coming from NativeBuilds.
41
+
For security critical libraries like OpenSSL this automation is very helpful and important.
42
+
43
+
If you're a library author:
44
+
This project also allows consumers of your library to update the underlying native library without you having to publish a new version of your own library.
45
+
Each static library (e.g. OpenSSL) is packaged like any other Kotlin module, so the normal Gradle dependency resolution rules apply.
46
+
It's even possible to substitute the static library with a debug version.
47
+
48
+
Finally, this project allows sharing/reusing the same underlying static library (e.g. OpenSSL or libcurl) in different projects.
49
+
For example, cryptography-kotlin could depend on libcrypto.a and Ktor's Curl engine could also depend on libcrypto.a (and libssl.a and libcurl.a) without causing duplication or symbol conflicts.
36
50
37
51
## Usage
38
52
@@ -80,16 +94,16 @@ kotlin {
80
94
api(libs.openssl.libcrypto)
81
95
}
82
96
83
-
// If you need direct access to the libcrypto/OpenSSL API you have to activate cinterop for the OpenSSL header files
97
+
// If you need direct access to the libcrypto/OpenSSL API you have to activate cinterop
98
+
// for the OpenSSL header files.
84
99
// Note: for zstd you'd use the libs.zstd both here and in sourceSets.nativeMain.
0 commit comments