Blame libnm-core/nm-libnm-core-aux/README.md
|
Packit Service |
b23acc |
nm-libnm-core-aux is a static library that:
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
- uses parts of "libnm-core", that are public API of "libnm"
|
|
Packit Service |
b23acc |
- can be statically linked into users of libnm-core (like libnm
|
|
Packit Service |
b23acc |
and NetworkManager).
|
|
Packit Service |
b23acc |
- that can also be statically linked into other users of libnm.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
Basically, it is a static library with utility functions that extends
|
|
Packit Service |
b23acc |
libnm-core (the part that is public API of libnm), but can also be
|
|
Packit Service |
b23acc |
used without full libnm.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
That means:
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
- you can use it everywhere where you either statically link
|
|
Packit Service |
b23acc |
with libnm-core, or dynamically link with libnm.
|
|
Packit Service |
b23acc |
- you cannot use it inside libnm-core itself. This is the difference
|
|
Packit Service |
b23acc |
between nm-libnm-core-intern and nm-libnm-core-aux.
|
|
Packit Service |
b23acc |
|
|
Packit Service |
b23acc |
Also, since nm-libnm-core-aux itself only uses public (stable)
|
|
Packit Service |
b23acc |
API of libnm, you theoretically can copy the sources into your
|
|
Packit Service |
b23acc |
own source tree.
|