fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2026-05-09 03:38:09 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/libnm-util/tests/Makefile.am

87 lines
1.7 KiB
Text
Raw Permalink Normal View History

build: improve documentation and test configure options Use --enable-doc and --enable-tests instead of --with-docs and --with-tests. This is consistent with other features and with --enable-gtk-doc option. Support current variants as fallback. Don't build tests unless --enable-tests is specified.
2012-11-05 11:35:34 +01:00
if ENABLE_TESTS
build: switch from $(INCLUDES) to $(AM_CPPFLAGS) to make automake happy Unfortunately, $(AM_CPPFLAGS) gets overridden by per-target _CPPFLAGS variables, which $(INCLUDES) did not, so this requires some additional changes. In most places, I have just gotten rid of the per-target _CPPFLAGS variables; in directories with a single target, the per-target variable is unnecessary, and in directories with multiple targets, the per-target variable is often undesirable, since it forces some files to be compiled twice, even though there ends up being no difference between the two files.
2013-08-22 10:47:21 -04:00
AM_CPPFLAGS = \
libnm-util: flag properties with G_PARAM_CONSTRUCT so default values get set This caused the 'autoconnect' property of NMSettingConnection to not get updated in some cases (as when a system setting plugin noticed a change to autoconnect=true and emitted the Updated signal, which wouldn't contain the new value). Add a testcase for setting default values too.
2009-02-01 20:18:21 -05:00
-I$(top_srcdir)/include \
build: extract version macros from "nm-version.h" to new header file "nm-version-macros.h" For libnm library, "nm-dbus-interface.h" contains defines like the D-Bus paths of NetworkManager. It is desirable to have this header usable without having a dependency on "glib.h", for example for a QT application. For that, commit c0852964a890cf43cc2dcaeff41ac6edc5028f24 removed that dependancy. For libnm-glib library, the analog to "nm-dbus-interface.h" is "NetworkManager.h", and the same applies there. Commit 159e827a72f420048e12d318f8ba1edd3f641fc8 removed that include. However, that broke build on PackageKit [1] which expected to get the version macros by including "NetworkManager.h". So at least for libnm-glib, we need to preserve old behavior so that a user including "NetworkManager.h" gets the version macros, but not "glib.h". Extract the version macros to a new header file "nm-version-macros.h". This header doesn't include "glib.h" and can be included from "NetworkManager.h". This gives as previous behavior and a glib-free include. For libnm we still don't include "nm-version-macros.h" to "nm-dbus-interface.h". Very few users will actually need the version macros, but not using libnm. Users that use libnm, should just include (libnm's) "NetworkManager.h" to get all headers. As a special case, a user who doesn't want to use glib/libnm, but still needs both "nm-dbus-interface.h" and "nm-version-macros.h", can include them both separately. [1] https://github.com/hughsie/PackageKit/issues/85 Fixes: 4545a7fe9670ce4d7c259c11c2cc853bfae6729b (cherry picked from commit 7bf10a75db84655e65fe6216d248f7775c58ca23)
2015-09-25 16:07:50 +02:00
-I$(top_builddir)/include \
build: fix srcdir != builddir for new generated headers
2012-02-22 16:37:38 -05:00
-I$(top_srcdir)/libnm-util \
build: switch from $(INCLUDES) to $(AM_CPPFLAGS) to make automake happy Unfortunately, $(AM_CPPFLAGS) gets overridden by per-target _CPPFLAGS variables, which $(INCLUDES) did not, so this requires some additional changes. In most places, I have just gotten rid of the per-target _CPPFLAGS variables; in directories with a single target, the per-target variable is unnecessary, and in directories with multiple targets, the per-target variable is often undesirable, since it forces some files to be compiled twice, even though there ends up being no difference between the two files.
2013-08-22 10:47:21 -04:00
-I$(top_builddir)/libnm-util \
libnm-util, libnm-glib: add versioned deprecation/availability macros Add versioned NM_DEPRECATED_IN_* and NM_AVAILABLE_IN_* macros, and tag new/deprecated functions accordingly. (All currently-deprecated functions are assumed to have been deprecated in 0.9.10.) Add NM_VERSION_MIN_REQUIRED and NM_VERSION_MAX_ALLOWED macros which can be set to determine which versions will cause warnings. With the current settings, external consumers of the libnm-util/libnm-glib APIs will have MIN_REQUIRED and MAX_ALLOWED both set to NM_VERSION_0_9_8 by default, meaning they will get warnings about functions added in 0.9.10. NM internally sets NM_VERSION_MAX_ALLOWED to NM_VERSION_NEXT_STABLE to ensure that it is always allowed to use all APIs.
2014-02-12 12:28:52 -05:00
-DNM_VERSION_MAX_ALLOWED=NM_VERSION_NEXT_STABLE \
build: switch from $(INCLUDES) to $(AM_CPPFLAGS) to make automake happy Unfortunately, $(AM_CPPFLAGS) gets overridden by per-target _CPPFLAGS variables, which $(INCLUDES) did not, so this requires some additional changes. In most places, I have just gotten rid of the per-target _CPPFLAGS variables; in directories with a single target, the per-target variable is unnecessary, and in directories with multiple targets, the per-target variable is often undesirable, since it forces some files to be compiled twice, even though there ends up being no difference between the two files.
2013-08-22 10:47:21 -04:00
$(GLIB_CFLAGS) \
$(DBUS_CFLAGS) \
libnm, libnm-utils: error out if mixed libnm/libnm-util symbols are detected If a program accidentally ends up linking in both libnm and libnm-util (presumably via different dependencies), error out immediately.
2014-07-25 17:50:14 -04:00
-DBUILD_DIR=\"$(abs_builddir)\" \
libnm-core, libnm-util: move test cert files to libnm-core/ Move the certificate files used by the libnm-util and libnm-core tests from libnm-util/tests/certs/ to libnm-core/tests/certs/.
2014-10-30 11:07:03 -04:00
-DTEST_CERT_DIR=\"$(top_srcdir)/libnm-core/tests/certs/\"
libnm-util: flag properties with G_PARAM_CONSTRUCT so default values get set This caused the 'autoconnect' property of NMSettingConnection to not get updated in some cases (as when a system setting plugin noticed a change to autoconnect=true and emitted the Updated signal, which wouldn't contain the new value). Add a testcase for setting default values too.
2009-02-01 20:18:21 -05:00
tests: enable valgrind tests for tests (cherry picked from commit c50f30e79c67593532392f0f251d662e4294f5b2)
2015-02-04 11:58:52 +01:00
@VALGRIND_RULES@
libnm-core, libnm-util: convert test-crypto, test-setting-8021x.c to gtestutils Rather than having test-crypto and test-setting-8021x be programs that you have to pass arguments to to get them to run a single test, just have them run all of the tests themselves. This lets us get rid of the big "check-local" rule in Makefile.am and just use TESTS to run everything. https://bugzilla.gnome.org/show_bug.cgi?id=734388
2014-08-06 20:19:07 -04:00
TESTS = \
libnm-util: don't allow blank or NULL VPN items or secrets (rh #532084) Weren't supposed to be allowed anyway; fix that and add a testcase for it.
2009-11-02 10:57:31 -08:00
test-settings-defaults \
test-crypto \
libnm-util: allow setting-only hashes with nm_connection_update_secrets() It's easier to be able to pass both a whole hashed connection, or just a hashed setting to the function, and have it figure out what needs to be updated based on the given setting_name. Add some testcases to make sure that all works correctly too.
2011-03-09 09:31:44 -06:00
test-secrets \
libnm-util: client certificate should not be required to set private key (bgo #585570) Not sure what I was thinking originally; there's no way this was correct in the first place.
2009-12-08 16:52:24 -08:00
test-general \
libnm-util: add Data Center Bridging (DCB) setting Includes various fixes & cleanups from Thomas Haller.
2013-09-13 09:44:56 -05:00
test-setting-8021x \
libnm-core, libnm-util: convert test-crypto, test-setting-8021x.c to gtestutils Rather than having test-crypto and test-setting-8021x be programs that you have to pass arguments to to get them to run a single test, just have them run all of the tests themselves. This lets us get rid of the big "check-local" rule in Makefile.am and just use TESTS to run everything. https://bugzilla.gnome.org/show_bug.cgi?id=734388
2014-08-06 20:19:07 -04:00
test-setting-dcb
noinst_PROGRAMS = \
$(TESTS) \
libnm, libnm-utils: error out if mixed libnm/libnm-util symbols are detected If a program accidentally ends up linking in both libnm and libnm-util (presumably via different dependencies), error out immediately.
2014-07-25 17:50:14 -04:00
test-libnm-linking
libnm-util: flag properties with G_PARAM_CONSTRUCT so default values get set This caused the 'autoconnect' property of NMSettingConnection to not get updated in some cases (as when a system setting plugin noticed a change to autoconnect=true and emitted the Updated signal, which wouldn't contain the new value). Add a testcase for setting default values too.
2009-02-01 20:18:21 -05:00
test_settings_defaults_SOURCES = \
test-settings-defaults.c
test_settings_defaults_LDADD = \
build: always link locally-built libraries first (bgo #580131)
2009-08-20 12:31:17 -05:00
$(top_builddir)/libnm-util/libnm-util.la \
makefile cleanups 0.7 requires dbus 1.1 or greater (for system bus activation), so make that explicit, and remove compat code for D-Bus 0.6 and earlier. Consolidate the various glib pkgconfig checks into one, since most anything will require gthread, glib, and gobject anyway. Fixup the docs makefile to be more automake-compatible and let 'make clean' actually work correctly when docs are built.
2009-02-15 11:20:25 -05:00
$(GLIB_LIBS) \
build: always link locally-built libraries first (bgo #580131)
2009-08-20 12:31:17 -05:00
$(DBUS_LIBS)
libnm-util: flag properties with G_PARAM_CONSTRUCT so default values get set This caused the 'autoconnect' property of NMSettingConnection to not get updated in some cases (as when a system setting plugin noticed a change to autoconnect=true and emitted the Updated signal, which wouldn't contain the new value). Add a testcase for setting default values too.
2009-02-01 20:18:21 -05:00
libnm-util: move crypto tests to libnm-util/tests/ Add testing certs and keys; run crypto tests on 'make check'
2009-02-02 01:03:15 -05:00
test_crypto_SOURCES = \
test-crypto.c
test_crypto_LDADD = \
build: always link locally-built libraries first (bgo #580131)
2009-08-20 12:31:17 -05:00
$(top_builddir)/libnm-util/libtest-crypto.la \
libnm-util: add nm_utils_rsa_key_encrypt() and fix crypto padding mixups To be backwards compatible clients need to handle both paths to private keys and the decrypted private key data, which is what used to get passed in the private-key and phase2-private-key attributes of the 802.1x setting. When moving a connection around between system-settings and user-settings, if the private key is decrypted data, the settings service needs to store that decrypted data somewhere so that the key can be sent to NM during the connection process. But we don't want to store the decrypted private key data, so we have to re-encrypt it (possibly generating a private key password if one wasn't sent with the decrypted data) and save it to disk, then send NM a path to that private key during connection. To help clients do this, and so that they don't have to carry around multiple crypto implementations depending on whether they want to use NSS or gnutls/gcrypt, add a helper to libnm-util. Furthermore, I misunderstood a bunch of stuff with crypto padding when writing the encrypt/decrypt functions long ago, so fix that up. Don't return padding as part of the decrypted data, and make sure to verify the padding's expected lengths and values when decrypting. Many thanks to Nalin Dahyabhai for pointing me in the right direction.
2009-09-15 16:01:50 -07:00
$(top_builddir)/libnm-util/libnm-util.la \
build: always link locally-built libraries first (bgo #580131)
2009-08-20 12:31:17 -05:00
$(GLIB_LIBS)
libnm-util: move crypto tests to libnm-util/tests/ Add testing certs and keys; run crypto tests on 'make check'
2009-02-02 01:03:15 -05:00
libnm-util: allow setting-only hashes with nm_connection_update_secrets() It's easier to be able to pass both a whole hashed connection, or just a hashed setting to the function, and have it figure out what needs to be updated based on the given setting_name. Add some testcases to make sure that all works correctly too.
2011-03-09 09:31:44 -06:00
test_secrets_SOURCES = \
test-secrets.c
libnm-util: fix checking for TLS and TTLS phase2 secrets Two errors here; first, need_secrets_tls() was not updated correctly for the certificate paths changes that landed recently, and would have incorrectly returned "no secrets required" for the PATH scheme. Second, an incorrect strcmp() comparison in need_secrets_phase2() meant that the wrong TTLS phase2 method would get asked if it required secrets.
2009-10-18 23:36:47 -07:00
libnm-util: allow setting-only hashes with nm_connection_update_secrets() It's easier to be able to pass both a whole hashed connection, or just a hashed setting to the function, and have it figure out what needs to be updated based on the given setting_name. Add some testcases to make sure that all works correctly too.
2011-03-09 09:31:44 -06:00
test_secrets_LDADD = \
libnm-util: fix checking for TLS and TTLS phase2 secrets Two errors here; first, need_secrets_tls() was not updated correctly for the certificate paths changes that landed recently, and would have incorrectly returned "no secrets required" for the PATH scheme. Second, an incorrect strcmp() comparison in need_secrets_phase2() meant that the wrong TTLS phase2 method would get asked if it required secrets.
2009-10-18 23:36:47 -07:00
$(top_builddir)/libnm-util/libnm-util.la \
$(GLIB_LIBS) \
$(DBUS_LIBS)
libnm-util: move crypto tests to libnm-util/tests/ Add testing certs and keys; run crypto tests on 'make check'
2009-02-02 01:03:15 -05:00
libnm-util: don't allow blank or NULL VPN items or secrets (rh #532084) Weren't supposed to be allowed anyway; fix that and add a testcase for it.
2009-11-02 10:57:31 -08:00
test_general_SOURCES = \
test-general.c
test_general_LDADD = \
$(top_builddir)/libnm-util/libnm-util.la \
$(GLIB_LIBS) \
$(DBUS_LIBS)
libnm, libnm-utils: error out if mixed libnm/libnm-util symbols are detected If a program accidentally ends up linking in both libnm and libnm-util (presumably via different dependencies), error out immediately.
2014-07-25 17:50:14 -04:00
test_general_DEPENDENCIES = test-libnm-linking
libnm-util: client certificate should not be required to set private key (bgo #585570) Not sure what I was thinking originally; there's no way this was correct in the first place.
2009-12-08 16:52:24 -08:00
test_setting_8021x_SOURCES = \
test-setting-8021x.c
test_setting_8021x_LDADD = \
$(top_builddir)/libnm-util/libnm-util.la \
$(GLIB_LIBS) \
$(DBUS_LIBS)
libnm-util: add Data Center Bridging (DCB) setting Includes various fixes & cleanups from Thomas Haller.
2013-09-13 09:44:56 -05:00
test_setting_dcb_SOURCES = \
test-setting-dcb.c
test_setting_dcb_LDADD = \
$(top_builddir)/libnm-util/libnm-util.la \
$(GLIB_LIBS) \
$(DBUS_LIBS)
libnm, libnm-utils: error out if mixed libnm/libnm-util symbols are detected If a program accidentally ends up linking in both libnm and libnm-util (presumably via different dependencies), error out immediately.
2014-07-25 17:50:14 -04:00
test_libnm_linking_SOURCES = \
test-libnm-linking.c
test_libnm_linking_LDADD = \
$(top_builddir)/libnm/libnm.la \
$(top_builddir)/libnm-util/libnm-util.la \
$(GLIB_LIBS) \
$(DBUS_LIBS)
libnm-util: flag properties with G_PARAM_CONSTRUCT so default values get set This caused the 'autoconnect' property of NMSettingConnection to not get updated in some cases (as when a system setting plugin noticed a change to autoconnect=true and emitted the Updated signal, which wouldn't contain the new value). Add a testcase for setting default values too.
2009-02-01 20:18:21 -05:00
endif
Reference in a new issue Copy permalink