NetworkManager/tools/Makefile.am

EXTRA_DIST = \
	check-exports.sh \
	create-exports-NetworkManager.sh \
	debug-helper.py \
	run-nm-test.sh \
	test-networkmanager-service.py \
	test-sudo-wrapper.sh \
	enums-to-docbook.pl
build: manpages-docbook.xsl should be DIST-ed 2013-02-05 12:16:34 -06:00			`EXTRA_DIST = \`
tools: dist everything Dist run-test-valgrind.sh and test-sudo-wrapper.sh, since they may be of use to people building from tarballs as well. 2014-07-25 11:53:15 -04:00			`check-exports.sh \`
tools: dist "tools/create-exports-NetworkManager.sh" It's also used by contrib/rpm's SPEC file. 2016-10-17 09:55:07 +02:00			`create-exports-NetworkManager.sh \`
tools: move debug-helper.py from test/ to tools/ 2014-07-25 11:54:36 -04:00			`debug-helper.py \`
tests: combine "run-test-valgrind.sh" and "run-test-dbus-session.sh" in "run-nm-test.sh" No need to have two test-runners. Combine them, and call tests always via "tools/run-nm-test.sh". Yes, this brings an overhead, that we now always invoke the test with a test wrapper script, also --without-vagrind. Previously, that was only necessary for libnm tests that require their own D-Bus session. Later we will do non-recursive Makefiles, thus all tests should have the same LOG_COMPILER. 2016-10-15 15:34:05 +02:00			`run-nm-test.sh \`
tools: move libnm-glib's fake NM service implementations here Move libnm-glib's test-fake-nm.py and test-remote-settings-service.py to tools/, merge them together into a single program, and fix a few bugs (notably some missing signal emissions in the Settings service). Although they are currently only used by libnm-glib's tests, they are generic enough that they could be used by other code in the future (and in particular, they will be used by libnm's tests as well). 2014-07-22 18:22:23 -04:00			`test-networkmanager-service.py \`
tools: add forgotten file to dist Fixes: f15c412015647b378a187bdf98ccf8cd75eb0475 2016-04-23 20:06:16 +02:00			`test-sudo-wrapper.sh \`
			`enums-to-docbook.pl`