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

42 lines
836 B
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 = \
build: rename directory "include" to "shared" Up to now, the "include" directory contained (only) header files that were used project-wide by libs, core, clients, et al. Since the directory now also contains a non-header file, the "include" name is misleading. Instead of adding yet another directory that is project-wide, with non-header-only content, rename the "include" directory to "shared".
2015-12-22 12:18:22 +01:00
-I$(top_srcdir)/shared \
-I$(top_builddir)/shared \
all: port everything to libnm Since the API has not changed at this point, this is mostly just a matter of updating Makefiles, and changing references to the library name in comments. NetworkManager cannot link to libnm due to the duplicated type/symbol names. So it links to libnm-core.la directly, which means that NetworkManager gets a separate copy of that code from libnm.so. Everything else links to libnm.
2014-05-19 13:44:02 -04:00
-I$(top_srcdir)/libnm-core \
-I$(top_builddir)/libnm-core \
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_srcdir)/callouts \
build: fix srcdir != builddir callouts/tests/ needs -I$(top_builddir)/callouts to get nmdbus-dispatcher.h
2014-10-24 14:40:33 -04:00
-I$(top_builddir)/callouts \
libnm: add NetworkManager.h, disallow including individual headers Add NetworkManager.h, which includes all of the other NM header, and require all external users of libnm to use that rather than the individual headers. (An exception is made for nm-dbus-interface.h, nm-vpn-dbus-interface.h, and nm-version.h, which can be included separately.)
2014-07-06 16:53:02 -04:00
-DNETWORKMANAGER_COMPILATION \
dispatcher: make test-dispatcher-envp not take an argument Compile srcdir into test-dispatcher-envp rather than passing it on the command-line, to make it easier to run by hand, and so we can use automake's TESTS support.
2014-09-18 11:34:21 -04:00
-DSRCDIR=\"$(abs_srcdir)\" \
core: final gdbus porting Port remaining bits to gdbus and remove stray dbus-glib references Drop the dbus-glib version check from configure, since nothing depends on new dbus-glib any more. Move nm-dbus-glib-types.h and nm-gvaluearray-compat.h from include/ to libnm-util/ since they are now only used by libnm-util and libnm-glib.
2015-04-16 12:34:55 -04:00
$(GLIB_CFLAGS)
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
noinst_PROGRAMS = \
test-dispatcher-envp
####### dispatcher envp #######
test_dispatcher_envp_SOURCES = \
test-dispatcher-envp.c
test_dispatcher_envp_LDADD = \
all: port everything to libnm Since the API has not changed at this point, this is mostly just a matter of updating Makefiles, and changing references to the library name in comments. NetworkManager cannot link to libnm due to the duplicated type/symbol names. So it links to libnm-core.la directly, which means that NetworkManager gets a separate copy of that code from libnm.so. Everything else links to libnm.
2014-05-19 13:44:02 -04:00
$(top_builddir)/libnm/libnm.la \
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
$(top_builddir)/callouts/libtest-dispatcher-envp.la \
core: final gdbus porting Port remaining bits to gdbus and remove stray dbus-glib references Drop the dbus-glib version check from configure, since nothing depends on new dbus-glib any more. Move nm-dbus-glib-types.h and nm-gvaluearray-compat.h from include/ to libnm-util/ since they are now only used by libnm-util and libnm-glib.
2015-04-16 12:34:55 -04:00
$(GLIB_LIBS)
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
###########################################
tests: enable valgrind tests for tests
2015-02-04 11:58:52 +01:00
@VALGRIND_RULES@
dispatcher: make test-dispatcher-envp not take an argument Compile srcdir into test-dispatcher-envp rather than passing it on the command-line, to make it easier to run by hand, and so we can use automake's TESTS support.
2014-09-18 11:34:21 -04:00
TESTS = test-dispatcher-envp
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
build: Don't conditionally omit files from distribution
2014-10-20 13:24:44 +02:00
endif
dispatcher: enhance dispatcher script environment (bgo #648382) For VPN connections, the interface name would be that of the VPN's IP interface, but the script environment would be the that of the VPN's parent device. Enhance the environment by adding any VPN specific details as additional environment variables prefixed by "VPN_". Leave the existing environment setup intact for backwards compatiblity. Additionally, the dispatcher never got updated for IPv6 support, so push IPv6 configuration and DHCPv6 configuration into the environment too. Even better, push everything the dispatcher needs to it instead of making the dispatcher make D-Bus requests back to NM, which sometimes fails if NM has already torn down the device or the connection which the device was using. And add some testcases to ensure that we don't break backwards compat, the testcases here were grabbed from a 0.8.4 machine with a hacked up dispatcher to dump everything it was given from NM.
2011-05-02 22:38:51 -05:00
EXTRA_DIST= \
nm-dispatcher: Handle the 'connectivity-state' parameter for 'Action' Actually handle this new parameter in the nm-dispatcher process, setting the value of a new CONNECTIVITY_STATE environment variable accordingly. This patch also includes new tests to check the different cases. https://bugzilla.gnome.org/show_bug.cgi?id=768969
2016-07-20 16:24:41 +01:00
dispatcher-connectivity-full \
dispatcher-connectivity-unknown \
dispatcher: remove "old" from the test names There's no reason the dispatcher test files should have "old" in their names, since they're testing the current dispatcher interface.
2014-12-18 08:35:58 -05:00
dispatcher-down \
dispatcher: add an env var indicating a connection is "external" Add CONNECTION_EXTERNAL=1 to the environment when dispatching actions on a "generated-assumed" connection (ie, one that was created outside of NM).
2014-12-18 09:13:57 -05:00
dispatcher-external \
dispatcher: remove "old" from the test names There's no reason the dispatcher test files should have "old" in their names, since they're testing the current dispatcher interface.
2014-12-18 08:35:58 -05:00
dispatcher-up \
dispatcher-vpn-down \
dispatcher-vpn-up
Reference in a new issue Copy permalink