9f4cd6b03f
For most strv or string properties, we cannot distinguish between NULL/unset/default and empty. It would be difficult to enter in nmcli or grasp how it differs. There are probably many bugs, where we accept empty strings, and fail to handle them correctly. Anyway. For most strv arrays, and empty array and NULL/unset/default are treated the same. That means, g_object_get() tends to always return NULL (never an empty strv array) and g_object_set() of an empty strv array will internally leave the GArray at NULL. For a few properties, there is a difference. See "ipv[46].dns-options". See also "clear_emptyunset_fcn" hook in libnm-setting. Add a way to handle such strv properties with the "direct" mechanism. |
||
|---|---|---|
| .. | ||
| meson.build | ||
| nm-core-internal.h | ||
| nm-keyfile-internal.h | ||
| nm-keyfile-utils.h | ||
| nm-meta-setting-base-impl.h | ||
| nm-meta-setting-base.h | ||
| README.md | ||
libnm-core-intern
This contains header files only, which are also part of
the internal API of libnm-core-impl.
libnm-core-impl is a static library that (among others) implements
libnm-core-public (which is a part of the public API of libnm).
This library gets statically linked into libnm and NetworkManager.
Hence, those components can also access internal (but not private) API of
libnm-core-impl, and this API is in libnm-core-intern.
These headers can thus be included by anybody who statically links with
libnm-core-impl (including libnm-core-impl itself).
The directory should not be added to the include search path, instead
users should explicitly #include "libnm-core-intern/nm-core-internal.h")
There is no source code here and no static library to link against.