mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-05-15 08:58:06 +02:00
723e1fc76f
libnm-core is also used by the daemon, thus currently dragging in libnm-crypto there. But could we ever drop that dependency? One use of the libnm-crypto is in functions like nm_utils_file_is_certificate() in "nm-utils.h". These are part of the public API of libnm. But this is not used by the daemon. Move it to "libnm-client-core" to be closer to where it's actually used. As we have unit tests in "libnm-core-impl/tests" that test this function, those unit tests also would need to move to "libnm-client-impl". Instead, add the actual implementation of these function to "libnm-crypto" and test it there. This patch moves forward declarations from public header "nm-utils.h" to "nm-client.h". Arguably, "nm-client.h" is not a great name, but we don't have a general purpose header in "libnm-client-public", so use this. Note that libnm users can only include <NetworkManager.h> and including individual files is not supported (and even prevented). Thus moving the declarations won't break any users. |
||
|---|---|---|
| .. | ||
| meson.build | ||
| nm-crypto-gnutls.c | ||
| nm-crypto-impl.h | ||
| nm-crypto-nss.c | ||
| nm-crypto-null.c | ||
| nm-crypto.c | ||
| nm-crypto.h | ||
| README.md | ||
libnm-crypto
libnm-core has a dependency on crypto code (either backed by "gnutls", "nss" or the "null" dummy implementation).
libnm-core gets then statically linked into the daemon and into libnm.so.