[gnutls-devel] GnuTLS | add cmake (!1908)
Read-only notification of GnuTLS library development activities
gnutls-devel at lists.gnutls.org
Thu Dec 19 21:05:08 CET 2024
Tal Regev commented: https://gitlab.com/gnutls/gnutls/-/merge_requests/1908#note_2268357813
After a discottion in https://gitlab.com/gnutls/gnutls/-/issues/320 I decided to create a PR to add a small compilation of the code in cmake.
This is a skeleton PR that can take and build up slowly the cmake build system.
I am not against Meson, I just more familiar with cmake.
Anyone can take this PR and continue / replace the work to fill the need for new build system. What I did with cmake, can be done similar with Meson.
This PR use the autoconf build system to compile. Because it needed the headers that it create. For not using the header the code will needed to change. This is not aim this PR and the follow. Only when the new build system will be large enough to replace autoconf, we can consider to change the code for that.
That is the big problem to replace autoconf. It needed to change to code to remove it. That why it cannot replace with one commit, and do a fork just for replace it just to much work. (the same just to do one big change of ci). The new build system need to build slowly side by side to autoconf, and live with the code. The code is dynamic change, and the build system need to adapt to that as well.
That why also the ci is needed and important. That why I added a compilation test in the ci.
--
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1908#note_2268357813
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20241219/7cdf42c8/attachment.html>
More information about the Gnutls-devel
mailing list