fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2026-01-05 09:10:17 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/src/Makefile.am

565 lines
15 KiB
Text
Raw Normal View History

core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
include $(GLIB_MAKEFILE)
Initial revision git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@2 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2004-06-24 14:18:37 +00:00
settings: add support for code coverage to the settings plugins Use: ./autogen.sh --enable-code-coverage make make -C src/settings check-code-coverage
2013-02-05 18:35:34 +01:00
@GNOME_CODE_COVERAGE_RULES@
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
SUBDIRS = \
. \
devices: rename "atm" plugin to "adsl", and "bt" to "bluetooth" The atm/adsl plugin really is a generic ATM plugin but (a) it needs a bit of work to do IPoATM rather than just PPPoATM and PPPoEoATM, and (b) most people currently using NM's ATM support are using DSL devices not actual ATM cards anyway, and have no idea what "ATM" even means. If we add the necessary IPoATM support later we can rename the plugin back to -atm
2014-03-19 14:16:48 -04:00
devices/adsl \
team: make team support a plugin Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-06-18 11:10:52 +02:00
devices/wifi \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
dhcp-manager \
ppp-manager \
settings/plugins
wwan, bluetooth: drop support for ModemManager 0.7
2014-05-20 16:36:42 -04:00
if WITH_MODEM_MANAGER_1
SUBDIRS += \
devices/wwan \
devices/bluetooth
endif
build: make WiMAX support optional
2011-01-05 18:23:08 -06:00
if WITH_WIMAX
core: move devices into a subdirectory We have lots of device types and will soon have lots more, so let's put them in their own directory.
2013-05-08 08:37:26 -04:00
SUBDIRS += devices/wimax
build: make WiMAX support optional
2011-01-05 18:23:08 -06:00
endif
team: remove conditional compilation WITH_TEAMDCTL teamdctl related parts are now in the device plugin src/devices/team/*. Remove the conditional compilation. Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-06-19 12:23:10 +02:00
if WITH_TEAMDCTL
SUBDIRS += devices/team
endif
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
if ENABLE_TESTS
trivial: allow building tests from rdisc directory The nm-rdisc subsystem, just as the nm-platform subsystem is separately testable and it proved convenient to be able to build the test programs by just typing 'make' in the rdisc/platform directory where the source code for those modules resides.
2013-07-29 14:44:49 +02:00
SUBDIRS += \
dhcp-manager/tests \
core: allow custom IP address ranges for Shared connections (bgo #675973) Given an IPv4 address and prefix for a shared config, figure out the DHCP address range automatically. To keep things simple we allow a max of 252 addresses (not including network address, broadcast address, and the hotspot) no matter what prefix you use, so if the address is 10.0.10.1, you still only get a range of 10.0.10.2 -> 10.0.10.254. But we also leave some addresses available above the host address for static stuff, like we did before. This is done on a sliding scale from 0 to 8 addresses, where about 1/10th the number of available addresses are reserved. https://bugzilla.gnome.org/show_bug.cgi?id=675973
2012-10-12 15:25:23 -05:00
dnsmasq-manager/tests \
trivial: allow building tests from rdisc directory The nm-rdisc subsystem, just as the nm-platform subsystem is separately testable and it proved convenient to be able to build the test programs by just typing 'make' in the rdisc/platform directory where the source code for those modules resides.
2013-07-29 14:44:49 +02:00
platform \
rdisc \
supplicant-manager/tests \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
tests
endif
core: add AddAndActivate D-Bus method Given connection details, complete the connection as well as possible using the given specific object and device, add it to system settings, and activate it all in one method.
2011-01-10 23:39:12 -06:00
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 = \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
-I$(top_srcdir)/include \
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 \
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
-I$(top_srcdir)/callouts \
core: consolidate helper progam searching (bgo #734131) Instead of having basically the same code in a bunch of different place to find helper programs, just have one place do it. Yes, this does mean that the same sequence of paths is searched for all helpers (so for example, dnsmasq will no longer be found first in /usr/local) but I think consistency is the better option here. https://bugzilla.gnome.org/show_bug.cgi?id=734131
2014-07-31 14:02:22 -05:00
-DPREFIX=\"$(prefix)\" \
all: set G_LOG_DOMAIN appropriately, for better g_log() messages
2014-04-07 16:14:47 -04:00
-DG_LOG_DOMAIN=\""NetworkManager"\" \
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 \
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
core: add AddAndActivate D-Bus method Given connection details, complete the connection as well as possible using the given specific object and device, add it to system settings, and activate it all in one method.
2011-01-10 23:39:12 -06:00
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
# add each subdirectory that contains a libNM source file. $(sort) is being used
# primarily for its side effect of removing duplicates.
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 += $(foreach d,$(sort $(dir $(libNetworkManager_la_SOURCES))),-I$(top_srcdir)/src/$d)
core: add AddAndActivate D-Bus method Given connection details, complete the connection as well as possible using the given specific object and device, add it to system settings, and activate it all in one method.
2011-01-10 23:39:12 -06:00
iface-helper: add nm-iface-helper for dynamic configure-then-quit support When quitting, the Manager asks each device to spawn the interface helper, which persists and manages dynamic address on the interface after NetworkManager is gone. If the dynamic address cannot be maintaned, the helper quits and the interface's address may be removed when their lifetime runs out. To keep the helper as simple as possible, NetworkManager passes most of the configuration on the command-line, including some properties of the device's current state, which are necessary for the helper to maintain DHCP leases or IPv6 SLAAC addresses.
2014-10-29 09:12:18 -05:00
noinst_LTLIBRARIES = \
libNetworkManager.la \
libnm-iface-helper.la \
libsystemd-dhcp.la
dhcp: add systemd-based "internal" DHCP client We must also remove -Waggregate-return from m4/compiler-warnings.m4 because systemd uses aggregate return (correctly) in a couple cases, and we cannot keep single-level makefiles and override aggregate-return only for the systemd sub-library. This client currently only supports DHCPv4 because the base systemd code does not yet fully support DHCPv6.
2014-07-22 12:38:20 -05:00
######################
# libsystemd-dhcp
######################
SYSTEMD_DHCP_CFLAGS = \
-I$(top_srcdir)/src/dhcp-manager/systemd-dhcp/src/systemd \
-I$(top_srcdir)/src/dhcp-manager/systemd-dhcp/src/libsystemd-network \
-I$(top_srcdir)/src/dhcp-manager/systemd-dhcp/src/shared \
-I$(top_srcdir)/src/dhcp-manager/systemd-dhcp
libsystemd_dhcp_la_SOURCES = \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp-network.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp-packet.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp-internal.h \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp6-network.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp6-lease-internal.h \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp6-option.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/network-internal.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/sd-dhcp-lease.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/sd-dhcp-client.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp-option.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/network-internal.h \
dhcp-manager/systemd-dhcp/src/libsystemd-network/sd-dhcp6-lease.c \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp-protocol.h \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp6-internal.h \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp6-protocol.h \
dhcp-manager/systemd-dhcp/src/libsystemd-network/dhcp-lease-internal.h \
dhcp-manager/systemd-dhcp/src/libsystemd-network/sd-dhcp6-client.c \
dhcp-manager/systemd-dhcp/src/shared/async.h \
dhcp-manager/systemd-dhcp/src/shared/time-util.h \
dhcp-manager/systemd-dhcp/src/shared/siphash24.h \
dhcp-manager/systemd-dhcp/src/shared/time-util.c \
dhcp-manager/systemd-dhcp/src/shared/socket-util.h \
dhcp-manager/systemd-dhcp/src/shared/sparse-endian.h \
dhcp-manager/systemd-dhcp/src/shared/macro.h \
dhcp-manager/systemd-dhcp/src/shared/refcnt.h \
dhcp-manager/systemd-dhcp/src/shared/util.c \
dhcp-manager/systemd-dhcp/src/shared/in-addr-util.c \
dhcp-manager/systemd-dhcp/src/shared/siphash24.c \
dhcp-manager/systemd-dhcp/src/shared/util.h \
dhcp-manager/systemd-dhcp/src/shared/in-addr-util.h \
dhcp-manager/systemd-dhcp/src/shared/list.h \
dhcp-manager/systemd-dhcp/src/shared/fileio.h \
dhcp-manager/systemd-dhcp/src/shared/fileio.c \
dhcp-manager/systemd-dhcp/src/shared/strv.h \
dhcp-manager/systemd-dhcp/src/shared/strv.c \
dhcp: re-fix system-dhcp code after re-import
2014-11-18 16:22:07 -05:00
dhcp-manager/systemd-dhcp/src/shared/unaligned.h \
dhcp: add systemd-based "internal" DHCP client We must also remove -Waggregate-return from m4/compiler-warnings.m4 because systemd uses aggregate return (correctly) in a couple cases, and we cannot keep single-level makefiles and override aggregate-return only for the systemd sub-library. This client currently only supports DHCPv4 because the base systemd code does not yet fully support DHCPv6.
2014-07-22 12:38:20 -05:00
dhcp-manager/systemd-dhcp/src/shared/utf8.h \
dhcp-manager/systemd-dhcp/src/shared/utf8.c \
dhcp-manager/systemd-dhcp/src/systemd/sd-dhcp-lease.h \
dhcp-manager/systemd-dhcp/src/systemd/sd-dhcp-client.h \
dhcp-manager/systemd-dhcp/src/systemd/sd-id128.h \
dhcp-manager/systemd-dhcp/src/systemd/sd-dhcp6-lease.h \
dhcp-manager/systemd-dhcp/src/systemd/sd-dhcp6-client.h \
dhcp-manager/systemd-dhcp/src/systemd/sd-event.h \
dhcp-manager/systemd-dhcp/src/systemd/_sd-common.h \
dhcp-manager/systemd-dhcp/nm-sd-adapt.h \
dhcp-manager/systemd-dhcp/nm-sd-adapt.c
libsystemd_dhcp_la_CPPFLAGS = \
-I$(top_srcdir)/include \
$(SYSTEMD_DHCP_CFLAGS) \
$(GLIB_CFLAGS)
libsystemd_dhcp_la_LIBADD = \
$(GLIB_LIBS)
fix distcheck for real
2009-02-02 01:36:43 -05:00
###########################################
# NetworkManager
###########################################
2006-01-20 Robert Love <rml@novell.com> * src/Makefile.am: Install the NetworkManager daemon to sbin, not bin. * dispatcher/Makefile.am: Install the NetworkManagerDispatcher daemon to sbin, not bin. git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1363 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-01-20 15:37:37 +00:00
sbin_PROGRAMS = NetworkManager
2004-11-12 Colin Walters <walters@redhat.com> * configure.in: Strip out TARGET_DISTRO and SYSTEM_BACKEND_FILE variables. Switch to Automake conditionals. * src/Makefile.am (noinst_LTLIBRARIES): Add libnmbackend.la. (libnmbackend_la_SOURCES): Use Automake conditionals to add distro-specific files. * initscript/Makefile.am (SUBDIRS): Update to use conditionals. git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@309 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2004-11-12 18:49:33 +00:00
bluetooth: NMDeviceBt and associated fixes
2009-05-14 11:01:56 -04:00
NetworkManager_SOURCES = \
build: ensure device source file constructors can be linked and called gcc's linker does not add constructors from object files to the main executable if they are built into a convenience library and then the library is linked to the executable, unless something outside of the object file with the constructor references a symbol from the object file. http://osdir.com/ml/libtool-gnu/2011-06/msg00003.html "Yes, when convenience libraries are used to create a shared library, all the objects are included in the output, when the output is an application they are used like a normal archive library. Either use them to create a shared library or, if creating an application, don't use them, use the objects instead." Further patches will remove all references to the NMDevice subclasses from nm-manager.c, and have each NMDevice subclass register itself with a factory through a constructor. But due to the above issue, we need to somehow ensure the constructor in each nm-device-*.c file gets added to the executable. This is accomplished by explicitly linking each NMDevice subclass' object file into the main executable. (Note that we cannot use -Wl,-whole-archive here because libtool only supports this option for linking a convenience library to a shared library, but not to an executable, and will actively prevent using -whole-archive in LDFLAGS)
2014-09-08 15:12:48 -05:00
$(nm_device_sources) $(nm_device_headers) \
dhcp: move client-specific knowledge out of the manager
2014-10-29 17:12:46 -05:00
$(nm_dhcp_client_sources) $(nm_dhcp_client_headers) \
core: split signal/pidfile/option handling into separate source file We'll use this from more than one spot.
2014-10-29 09:36:47 -05:00
main-utils.c \
main-utils.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
main.c
core: fix libndp linking We were linking libndp into the NetworkManager binary, but it ought to be marked as a dependency of libNetworkManager, in case a test exercises that code.
2014-07-17 18:04:17 -04:00
NetworkManager_LDADD = libNetworkManager.la
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
build: ensure device source file constructors can be linked and called gcc's linker does not add constructors from object files to the main executable if they are built into a convenience library and then the library is linked to the executable, unless something outside of the object file with the constructor references a symbol from the object file. http://osdir.com/ml/libtool-gnu/2011-06/msg00003.html "Yes, when convenience libraries are used to create a shared library, all the objects are included in the output, when the output is an application they are used like a normal archive library. Either use them to create a shared library or, if creating an application, don't use them, use the objects instead." Further patches will remove all references to the NMDevice subclasses from nm-manager.c, and have each NMDevice subclass register itself with a factory through a constructor. But due to the above issue, we need to somehow ensure the constructor in each nm-device-*.c file gets added to the executable. This is accomplished by explicitly linking each NMDevice subclass' object file into the main executable. (Note that we cannot use -Wl,-whole-archive here because libtool only supports this option for linking a convenience library to a shared library, but not to an executable, and will actively prevent using -whole-archive in LDFLAGS)
2014-09-08 15:12:48 -05:00
nm_device_sources = \
bond: port to internal device factory
2014-09-08 10:15:02 -05:00
devices/nm-device-bond.c \
bridge: port to internal device factory
2014-09-08 10:12:28 -05:00
devices/nm-device-bridge.c \
ethernet: port to internal device factory
2014-09-10 10:59:40 -05:00
devices/nm-device-ethernet.c \
gre: port to internal device factory
2014-09-08 11:17:58 -05:00
devices/nm-device-gre.c \
infiniband: port to internal device factory
2014-09-05 16:07:43 -05:00
devices/nm-device-infiniband.c \
macvlan: port to internal device factory
2014-09-08 11:11:19 -05:00
devices/nm-device-macvlan.c \
tun: port to internal device factory
2014-09-08 11:50:37 -05:00
devices/nm-device-tun.c \
veth: port to internal device factory We must port NMDeviceVeth before NMDeviceEthernet because veth is an ethernet subclass and uses symbols from nm-device-ethernet.c.
2014-09-08 10:57:31 -05:00
devices/nm-device-veth.c \
vlan: port to internal device factory
2014-09-08 10:24:11 -05:00
devices/nm-device-vlan.c \
vxlan: port to internal device factory
2014-09-08 11:13:42 -05:00
devices/nm-device-vxlan.c \
build: ensure device source file constructors can be linked and called gcc's linker does not add constructors from object files to the main executable if they are built into a convenience library and then the library is linked to the executable, unless something outside of the object file with the constructor references a symbol from the object file. http://osdir.com/ml/libtool-gnu/2011-06/msg00003.html "Yes, when convenience libraries are used to create a shared library, all the objects are included in the output, when the output is an application they are used like a normal archive library. Either use them to create a shared library or, if creating an application, don't use them, use the objects instead." Further patches will remove all references to the NMDevice subclasses from nm-manager.c, and have each NMDevice subclass register itself with a factory through a constructor. But due to the above issue, we need to somehow ensure the constructor in each nm-device-*.c file gets added to the executable. This is accomplished by explicitly linking each NMDevice subclass' object file into the main executable. (Note that we cannot use -Wl,-whole-archive here because libtool only supports this option for linking a convenience library to a shared library, but not to an executable, and will actively prevent using -whole-archive in LDFLAGS)
2014-09-08 15:12:48 -05:00
$(NULL)
nm_device_headers = \
devices/nm-device-bond.h \
devices/nm-device-bridge.h \
devices/nm-device-ethernet.h \
devices/nm-device-gre.h \
devices/nm-device-infiniband.h \
devices/nm-device-macvlan.h \
devices/nm-device-tun.h \
devices/nm-device-veth.h \
devices/nm-device-vlan.h \
devices/nm-device-vxlan.h
dhcp: move client-specific knowledge out of the manager
2014-10-29 17:12:46 -05:00
nm_dhcp_client_sources = \
dhcp-manager/nm-dhcp-dhclient.c \
dhcp-manager/nm-dhcp-dhclient-utils.c \
dhcp-manager/nm-dhcp-dhcpcd.c \
dhcp-manager/nm-dhcp-systemd.c
nm_dhcp_client_headers = \
dhcp-manager/nm-dhcp-dhclient.h \
dhcp-manager/nm-dhcp-dhclient-utils.h \
dhcp-manager/nm-dhcp-dhcpcd.h \
dhcp-manager/nm-dhcp-systemd.h
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm_sources = \
build: ensure device source file constructors can be linked and called gcc's linker does not add constructors from object files to the main executable if they are built into a convenience library and then the library is linked to the executable, unless something outside of the object file with the constructor references a symbol from the object file. http://osdir.com/ml/libtool-gnu/2011-06/msg00003.html "Yes, when convenience libraries are used to create a shared library, all the objects are included in the output, when the output is an application they are used like a normal archive library. Either use them to create a shared library or, if creating an application, don't use them, use the objects instead." Further patches will remove all references to the NMDevice subclasses from nm-manager.c, and have each NMDevice subclass register itself with a factory through a constructor. But due to the above issue, we need to somehow ensure the constructor in each nm-device-*.c file gets added to the executable. This is accomplished by explicitly linking each NMDevice subclass' object file into the main executable. (Note that we cannot use -Wl,-whole-archive here because libtool only supports this option for linking a convenience library to a shared library, but not to an executable, and will actively prevent using -whole-archive in LDFLAGS)
2014-09-08 15:12:48 -05:00
$(nm_device_headers) \
dhcp: move client-specific knowledge out of the manager
2014-10-29 17:12:46 -05:00
$(nm_dhcp_client_headers) \
core: move devices into a subdirectory We have lots of device types and will soon have lots more, so let's put them in their own directory.
2013-05-08 08:37:26 -04:00
devices/nm-device.c \
devices/nm-device.h \
settings: create default wired connection from NMDeviceEthernet Instead of creating it in NMSettings, where we must use NM_IS_DEVICE_ETHERNET() (not NM_DEVICE_TYPE_ETHERNET because various generic devices masquerade as NM_DEVICE_TYPE_ETHERNET too), push knowledge of which device types create default wired connections into the device types themselves. This solves a problem with testcases where libNetworkManager.a (which testcases link to) requires the symbol nm_type_device_ethernet().
2014-09-08 16:11:51 -05:00
devices/nm-device-ethernet-utils.c \
devices/nm-device-ethernet-utils.h \
devices: rework device plugin interface to be more flexible In preparation for making WWAN and Bluetooth plugins, rework the device plugin interface to meet those plugins' needs and port WiMAX over in the process.
2014-02-09 10:22:19 -06:00
devices/nm-device-factory.c \
core: move devices into a subdirectory We have lots of device types and will soon have lots more, so let's put them in their own directory.
2013-05-08 08:37:26 -04:00
devices/nm-device-factory.h \
devices/nm-device-generic.c \
devices/nm-device-generic.h \
logging: extract logging macros for devices to nm-device-logging.h Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-08-02 14:52:49 +02:00
devices/nm-device-logging.h \
core: move devices into a subdirectory We have lots of device types and will soon have lots more, so let's put them in their own directory.
2013-05-08 08:37:26 -04:00
devices/nm-device-private.h \
\
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
dhcp-manager/nm-dhcp-client.c \
dhcp-manager/nm-dhcp-client.h \
dhcp: split out DHCP options processing No code changed except passing what used to use "priv->" as function parameters.
2014-07-01 08:21:33 -05:00
dhcp-manager/nm-dhcp-utils.c \
dhcp-manager/nm-dhcp-utils.h \
dhcp: move D-Bus DHCP listener into separate class This simplifies the manager and ensures that only the clients that use D-Bus-based DHCP helpers need to care about them.
2014-10-29 15:04:38 -05:00
dhcp-manager/nm-dhcp-listener.c \
dhcp-manager/nm-dhcp-listener.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
dhcp-manager/nm-dhcp-manager.c \
dhcp-manager/nm-dhcp-manager.h \
\
dns-manager/nm-dns-dnsmasq.c \
dns-manager/nm-dns-dnsmasq.h \
dns: preliminary support for unbound (bgo #699810) The script is called synchronously from NetworkManager so it can handle asynchronicity itself. The long-term plan is to incorporate the script partially into the new plugin and partially into a dnssec-trigger library which will be used instead of dnssec-trigger daemon. https://bugzilla.gnome.org/show_bug.cgi?id=699810 Acked-By: Thomas Haller <thaller@redhat.com> Acked-By: Dan Williams <dcbw@redhat.com>
2014-04-03 12:39:45 +02:00
dns-manager/nm-dns-unbound.c \
dns-manager/nm-dns-unbound.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
dns-manager/nm-dns-manager.c \
dns-manager/nm-dns-manager.h \
dns-manager/nm-dns-plugin.c \
dns-manager/nm-dns-plugin.h \
dns-manager/nm-dns-utils.c \
dns-manager/nm-dns-utils.h \
\
dnsmasq-manager/nm-dnsmasq-manager.c \
dnsmasq-manager/nm-dnsmasq-manager.h \
core: allow custom IP address ranges for Shared connections (bgo #675973) Given an IPv4 address and prefix for a shared config, figure out the DHCP address range automatically. To keep things simple we allow a max of 252 addresses (not including network address, broadcast address, and the hotspot) no matter what prefix you use, so if the address is 10.0.10.1, you still only get a range of 10.0.10.2 -> 10.0.10.254. But we also leave some addresses available above the host address for static stuff, like we did before. This is done on a sliding scale from 0 to 8 addresses, where about 1/10th the number of available addresses are reserved. https://bugzilla.gnome.org/show_bug.cgi?id=675973
2012-10-12 15:25:23 -05:00
dnsmasq-manager/nm-dnsmasq-utils.c \
dnsmasq-manager/nm-dnsmasq-utils.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
\
platform/nm-fake-platform.c \
platform/nm-fake-platform.h \
platform/nm-linux-platform.c \
platform/nm-linux-platform.h \
platform/nm-platform.c \
platform/nm-platform.h \
wifi: move wifi-utils into platform Move wifi-utils into NMPlatform, and update callers to use the new NMPlatform wrappers
2014-02-04 14:27:03 +01:00
platform/wifi/wifi-utils-nl80211.c \
platform/wifi/wifi-utils-nl80211.h \
platform/wifi/wifi-utils-private.h \
platform/wifi/wifi-utils.c \
platform/wifi/wifi-utils.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
\
device: use internal router discovery implementation
2013-05-30 16:53:23 +02:00
rdisc/nm-fake-rdisc.c \
rdisc/nm-fake-rdisc.h \
rdisc/nm-lndp-rdisc.c \
rdisc/nm-lndp-rdisc.h \
rdisc/nm-rdisc.c \
rdisc/nm-rdisc.h \
rdisc: move most RA processing logic into base class Instead of having it all in the Linux implementation, move all the timeout logic and most of the processing logic into the NMRDisc base class so that it can be used by NMFakeRDisc as well. This will help increase testability since now we can test the timeout and expiry logic from the fake plugin too.
2015-04-09 13:28:09 -05:00
rdisc/nm-rdisc-private.h \
device: use internal router discovery implementation
2013-05-30 16:53:23 +02:00
\
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
ppp-manager/nm-ppp-manager.c \
ppp-manager/nm-ppp-manager.h \
ppp-manager/nm-ppp-status.h \
\
settings/nm-agent-manager.c \
settings/nm-agent-manager.h \
settings/nm-inotify-helper.c \
settings/nm-inotify-helper.h \
settings/nm-secret-agent.c \
settings/nm-secret-agent.h \
settings/nm-settings-connection.c \
settings/nm-settings-connection.h \
settings/nm-settings.c \
settings/nm-settings.h \
settings/nm-system-config-interface.c \
settings/nm-system-config-interface.h \
\
settings/plugins/keyfile/common.h \
settings/plugins/keyfile/nm-keyfile-connection.c \
settings/plugins/keyfile/nm-keyfile-connection.h \
settings/plugins/keyfile/plugin.c \
settings/plugins/keyfile/plugin.h \
settings/plugins/keyfile/reader.c \
settings/plugins/keyfile/reader.h \
settings/plugins/keyfile/utils.c \
settings/plugins/keyfile/utils.h \
settings/plugins/keyfile/writer.c \
settings/plugins/keyfile/writer.h \
\
supplicant-manager/nm-supplicant-config.c \
supplicant-manager/nm-supplicant-config.h \
supplicant-manager/nm-supplicant-interface.c \
supplicant-manager/nm-supplicant-interface.h \
supplicant-manager/nm-supplicant-manager.c \
supplicant-manager/nm-supplicant-manager.h \
supplicant-manager/nm-supplicant-settings-verify.c \
supplicant-manager/nm-supplicant-settings-verify.h \
supplicant-manager/nm-supplicant-types.h \
wifi: move NMCallStore to the supplicant code Which is the only place it's used.
2013-06-04 18:30:20 -05:00
supplicant-manager/nm-call-store.c \
supplicant-manager/nm-call-store.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
\
vpn-manager/nm-vpn-connection.c \
vpn-manager/nm-vpn-connection.h \
vpn-manager/nm-vpn-manager.c \
vpn-manager/nm-vpn-manager.h \
vpn-manager/nm-vpn-service.c \
vpn-manager/nm-vpn-service.h \
\
nm-activation-request.c \
nm-activation-request.h \
nm-active-connection.c \
nm-active-connection.h \
core: merge src/config, src/logging, src/posix-signals into src/ Some subdirectories of src/ encapsulate large chunks of functionality, but src/config/, src/logging/, and src/posix-signals/ are really only separated out because they used to be built into separate sub-libraries that were needed either for test programs, or to prevent circular dependencies. Since this is no longer relevant, simplify things by moving their files back into the main source directory.
2014-07-25 12:04:04 -04:00
nm-config.c \
nm-config.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
nm-connection-provider.c \
nm-connection-provider.h \
core: build NMConnectivity unconditionally, possibly as a no-op Build and use NMConnectivity regardless of build options; if you build without libsoup, NMConnectivity will just always report that you have full connectivity (like it does when you build with libsoup but don't enable connectivity checking).
2013-07-29 16:36:00 -04:00
nm-connectivity.c \
nm-connectivity.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
nm-dbus-manager.c \
nm-dbus-manager.h \
core: add dcbtool manipulation logic
2013-10-03 23:42:26 -05:00
nm-dcb.c \
nm-dcb.h \
policy: add manager for default routes and support multiple default routes Up to now, NMPolicy would iterate over all devices to find the "best" device and assign the default route to that device. A better approach is to add a default route to *all* devices that are never-default=no. The relative priority is choosen according to the route metrics. If two devices receive the same metric, we want to prefer the device that activates first. That way, the default route sticks to the same device until a better device activates or the device deactivates. Hence, the order of activation is imporant in this case (as it is already now). Also, if several devices have identical metrics, increment their metrics so that every metric is unique. This makes the routing deterministic according to what we choose as best device. A special case is assumed devices. In this case we cannot adjust the metric in face of equal metrics. Add a new singleton class NMDefaultRouteManager that has a list of all devices and their default routes. The manager will order the devices by their priority and configure the routes using platform. Also update the metric for VPN connections. Later we will track VPN routes also via NMDefaultRouteManager. For now, fix the VPN metric because otherwise VPNs would always get metric 1024 (which is usually much larger then the device metrics). https://bugzilla.gnome.org/show_bug.cgi?id=735512 Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-08-29 00:03:47 +02:00
nm-default-route-manager.c \
nm-default-route-manager.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
nm-dhcp4-config.c \
nm-dhcp4-config.h \
nm-dhcp6-config.c \
nm-dhcp6-config.h \
nm-dispatcher.c \
nm-dispatcher.h \
nm-enum-types.c \
nm-enum-types.h \
core: move content of src/firewall-manager directory to src/ The directory firewall-manager/ only contained one source and one header file. Move them to the parent src/ directory. Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-11-12 12:37:12 +01:00
nm-firewall-manager.c \
nm-firewall-manager.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
nm-ip4-config.c \
nm-ip4-config.h \
nm-ip6-config.c \
nm-ip6-config.h \
core: merge src/config, src/logging, src/posix-signals into src/ Some subdirectories of src/ encapsulate large chunks of functionality, but src/config/, src/logging/, and src/posix-signals/ are really only separated out because they used to be built into separate sub-libraries that were needed either for test programs, or to prevent circular dependencies. Since this is no longer relevant, simplify things by moving their files back into the main source directory.
2014-07-25 12:04:04 -04:00
nm-logging.c \
nm-logging.h \
auth: rework polkit autorization to use DBUS interface directly This makes NetworkManager independent of <polkit/polkit.h> development headers and libpolkit-gobject-1.so library. Instead communicate directly with polkit using its DBUS interface. PolicyKit support is now always compiled in. You can control polkit authorization with the configuration option [main] auth-polkit=yes|no If the configure option is omitted, a build time default value is used. This default value can be set with the configure option --enable-polkit. This commit adds a new class NMAuthManager that reimplements the relevant DBUS client parts. It takes source code from the polkit library. https://bugzilla.gnome.org/show_bug.cgi?id=734146 Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-08-14 13:34:57 +02:00
nm-auth-manager.c \
nm-auth-manager.h \
core: add NMAuthSubject object to encapsulate authentication info This object encapsulates all authentication information we need about some entity that requests that NetworkManager perform an action on its behalf.
2013-07-25 22:53:43 -05:00
nm-auth-subject.c \
nm-auth-subject.h \
auth: rename file nm-manager-auth.* to nm-auth-utils.* Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-08-16 01:33:46 +02:00
nm-auth-utils.c \
nm-auth-utils.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
nm-manager.c \
nm-manager.h \
nm-policy.c \
nm-policy.h \
core: merge src/config, src/logging, src/posix-signals into src/ Some subdirectories of src/ encapsulate large chunks of functionality, but src/config/, src/logging/, and src/posix-signals/ are really only separated out because they used to be built into separate sub-libraries that were needed either for test programs, or to prevent circular dependencies. Since this is no longer relevant, simplify things by moving their files back into the main source directory.
2014-07-25 12:04:04 -04:00
nm-posix-signals.c \
nm-posix-signals.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
nm-properties-changed-signal.c \
nm-properties-changed-signal.h \
core: split NMRfkillManager out of NMUdevManager Split the rfkill-monitoring parts of NMUdevManager into a separate class. Now NMUdevManager only handles device enumeration.
2013-05-09 10:24:08 -04:00
nm-rfkill-manager.c \
nm-rfkill-manager.h \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
nm-session-monitor.h \
nm-session-utils.c \
nm-session-utils.h \
nm-sleep-monitor.h \
nm-types.h \
NetworkManagerUtils.c \
NetworkManagerUtils.h
core: make connectivity checking selectable at build-time Just in case you really don't want to install libsoup.
2011-12-05 15:11:13 -06:00
build: easier selection of session tracking Using --with-session-tracking=xxx you can select the backend you want from among CK, systemd, or none.
2012-02-01 16:49:46 -06:00
if SESSION_TRACKING_SYSTEMD
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm_sources += nm-session-monitor-systemd.c
build: easier selection of session tracking Using --with-session-tracking=xxx you can select the backend you want from among CK, systemd, or none.
2012-02-01 16:49:46 -06:00
else
if SESSION_TRACKING_CK
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm_sources += nm-session-monitor-ck.c
core: optionally use systemd for session tracking instead of ConsoleKit When configured with --enable-systemd, this patch makes NetworkManager use systemd for session tracking instead of ConsoleKit.
2011-12-23 20:07:07 -05:00
else
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm_sources += nm-session-monitor-null.c
build: easier selection of session tracking Using --with-session-tracking=xxx you can select the backend you want from among CK, systemd, or none.
2012-02-01 16:49:46 -06:00
endif
build: decouple systemd session tracking from systemd suspend/resume New option --with-suspend-resume=[upower|systemd] which defaults to systemd if you have systemd >= 183 with the inhibit support, otherwise upower. Allows you to use systemd session tracking simultaneously with upower for suspend/resume if you don't have system >= 183.
2012-11-06 14:22:44 -06:00
endif
core: add a systemd suspend/resume monitor (bgo #677694) This implementation uses a delay inhibitor to get systemd to emit PrepareForSleep, and then emits ::Sleeping and ::Resuming when receiving the before/after PrepareForSleep emissions.
2012-10-09 00:39:03 -04:00
build: decouple systemd session tracking from systemd suspend/resume New option --with-suspend-resume=[upower|systemd] which defaults to systemd if you have systemd >= 183 with the inhibit support, otherwise upower. Allows you to use systemd session tracking simultaneously with upower for suspend/resume if you don't have system >= 183.
2012-11-06 14:22:44 -06:00
if SUSPEND_RESUME_SYSTEMD
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm_sources += nm-sleep-monitor-systemd.c
build: decouple systemd session tracking from systemd suspend/resume New option --with-suspend-resume=[upower|systemd] which defaults to systemd if you have systemd >= 183 with the inhibit support, otherwise upower. Allows you to use systemd session tracking simultaneously with upower for suspend/resume if you don't have system >= 183.
2012-11-06 14:22:44 -06:00
else
core: add a systemd suspend/resume monitor (bgo #677694) This implementation uses a delay inhibitor to get systemd to emit PrepareForSleep, and then emits ::Sleeping and ::Resuming when receiving the before/after PrepareForSleep emissions.
2012-10-09 00:39:03 -04:00
# UPower suspend/resume used whenever systemd is not enabled
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm_sources += nm-sleep-monitor-upower.c
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
endif
if WITH_WEXT
wifi: move wifi-utils into platform Move wifi-utils into NMPlatform, and update callers to use the new NMPlatform wrappers
2014-02-04 14:27:03 +01:00
nm_sources += \
platform/wifi/wifi-utils-wext.c \
platform/wifi/wifi-utils-wext.h
core: optionally use systemd for session tracking instead of ConsoleKit When configured with --enable-systemd, this patch makes NetworkManager use systemd for session tracking instead of ConsoleKit.
2011-12-23 20:07:07 -05:00
endif
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
GLIB_GENERATED = nm-enum-types.h nm-enum-types.c
libnm-core, settings: move NMAgentManagerError to nm-errors Move the definition of NMAgentManagerError to nm-errors, register it with D-Bus, and verify in the tests that it maps correctly.
2014-10-15 15:27:25 -04:00
GLIB_MKENUMS_H_FLAGS = --identifier-prefix NM --fhead '\#include <nm-core-enum-types.h>\n'
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
GLIB_MKENUMS_C_FLAGS = --identifier-prefix NM
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm_enum_types_sources = $(nm_sources)
bluez: make Bluetooth support a plugin Make Bluetooth support a plugin using the new device factory interface. Provides a 5% size reduction in the core NM binary. Before After NM: 1253016 1187224 (-5%) BT: 0 85752 (all results from stripped files)
2014-02-10 06:35:56 -06:00
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
if WITH_WIMAX
core: move devices into a subdirectory We have lots of device types and will soon have lots more, so let's put them in their own directory.
2013-05-08 08:37:26 -04:00
nm_enum_types_sources += devices/wimax/nm-device-wimax.h
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 += -I$(top_srcdir)/src/devices/wimax
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
endif
2006-02-02 Robert Love <rml@novell.com> * src/Makefile.am: If we aren't going to create the run directory at, uh, run-time, create it during install. Then users just doing 'make install' are cool, too. While we are here, create the dispatcher.d directory, too. * src/nm-device-802-11-wireless.c: Let the Makefile define and pass in the exact run directory. * Makefile.am: Install nm-applet.desktop. git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1430 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-02-02 20:52:43 +00:00
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
BUILT_SOURCES = $(GLIB_GENERATED)
glue_sources = \
nm-access-point-glue.h \
nm-active-connection-glue.h \
nm-agent-manager-glue.h \
nm-device-bond-glue.h \
nm-device-bridge-glue.h \
nm-device-ethernet-glue.h \
nm-device-generic-glue.h \
nm-device-glue.h \
platform, devices: add support for gre and gretap devices
2013-05-21 12:49:24 -03:00
nm-device-gre-glue.h \
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm-device-infiniband-glue.h \
platform, devices: add support for macvlan and macvtap devices
2013-05-06 09:16:17 -04:00
nm-device-macvlan-glue.h \
platform, devices: add support for tun and tap devices
2013-04-25 15:46:39 -04:00
nm-device-tun-glue.h \
platform, devices: add support for veth devices https://bugzilla.gnome.org/show_bug.cgi?id=687254
2013-05-03 13:55:51 -04:00
nm-device-veth-glue.h \
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm-device-vlan-glue.h \
platform, devices: add support for vxlan devices Since vxlan is new-ish, and vxlan IPv6 support in particular has only been in the kernel since 3.11, we include our own copy of the vxlan netlink constants rather than depending on the installed headers.
2013-06-04 10:31:22 -03:00
nm-device-vxlan-glue.h \
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
nm-dhcp4-config-glue.h \
nm-dhcp6-config-glue.h \
nm-ip4-config-glue.h \
nm-ip6-config-glue.h \
nm-manager-glue.h \
nm-ppp-manager-glue.h \
nm-settings-connection-glue.h \
nm-settings-glue.h \
nm-vpn-connection-glue.h
BUILT_SOURCES += $(glue_sources)
%-glue.h: $(top_srcdir)/introspection/%.xml
$(AM_V_GEN) dbus-binding-tool --prefix=$(subst -,_,$(subst -glue.h,,$@)) --mode=glib-server --output=$@ $<
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 += \
bluetooth: add bluetooth manager
2009-05-13 21:32:56 -04:00
$(DBUS_CFLAGS) \
$(GLIB_CFLAGS) \
rfkill: port rfkill to libgudev
2009-06-05 01:55:02 -04:00
$(GUDEV_CFLAGS) \
bluetooth: add bluetooth manager
2009-05-13 21:32:56 -04:00
$(LIBNL_CFLAGS) \
device: use internal router discovery implementation
2013-05-30 16:53:23 +02:00
$(LIBNDP_CFLAGS) \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
$(LIBSOUP_CFLAGS) \
build: clarify systemd-login build flags systemd gets used for more than just systemd-login.
2012-11-06 14:11:05 -06:00
$(SYSTEMD_LOGIN_CFLAGS) \
dhcp: add systemd-based "internal" DHCP client We must also remove -Waggregate-return from m4/compiler-warnings.m4 because systemd uses aggregate return (correctly) in a couple cases, and we cannot keep single-level makefiles and override aggregate-return only for the systemd sub-library. This client currently only supports DHCPv4 because the base systemd code does not yet fully support DHCPv6.
2014-07-22 12:38:20 -05:00
$(SYSTEMD_DHCP_CFLAGS) \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
\
bluetooth: add bluetooth manager
2009-05-13 21:32:56 -04:00
-DBINDIR=\"$(bindir)\" \
-DDATADIR=\"$(datadir)\" \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
-DLIBEXECDIR=\"$(libexecdir)\" \
bluetooth: add bluetooth manager
2009-05-13 21:32:56 -04:00
-DLOCALSTATEDIR=\"$(localstatedir)\" \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
-DSBINDIR=\"$(sbindir)\" \
-DSYSCONFDIR=\"$(sysconfdir)\" \
dhcp: dhcpcd uses a fixed path for PID files It always uses RUNDIR and the change to NMRUNDIR was in error. This could cause NetworkManager not to be able to kill old dhcpcd processes.
2013-11-27 19:00:14 -06:00
-DRUNDIR=\"$(rundir)\" \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
\
-DNMCONFDIR=\"$(nmconfdir)\" \
bluetooth: add bluetooth manager
2009-05-13 21:32:56 -04:00
-DNMLOCALEDIR=\"$(datadir)/locale\" \
build: unify NetworkManager path handling (some paths are changed) Use autoconf/automake variables for NetworkManager paths. Use NetworkManager subdirectory where appropriate. Files in /var/run (or /run on some distros) are moved into a separate directory as is usual with other daemons. It makes the filesystem more readable and file prefixing unnecessary. /var/run/NetworkManager.pid -> /var/run/NetworkManager/NetworkManager.pid /var/run/nm-dns-dnsmasq.pid -> /var/run/NetworkManager/dnsmasq.pid /var/run/nm-dns-dnsmasq.conf -> /var/run/NetworkManager/dnsmasq.conf The /var/run/NetworkManager directory is created at runtime, if it doesn't exist. Note: Path-based security policies like SELinux and AppArmor may need to be adapted.
2012-08-23 11:53:41 +02:00
-DNMPLUGINDIR=\"$(pkglibdir)\" \
-DNMRUNDIR=\"$(nmrundir)\" \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
-DNMSTATEDIR=\"$(nmstatedir)\" \
\
-DDHCLIENT_PATH=\"$(DHCLIENT_PATH)\" \
-DDHCPCD_PATH=\"$(DHCPCD_PATH)\" \
-DPPPD_PLUGIN_DIR=\"$(PPPD_PLUGIN_DIR)\" \
\
$(NULL)
core: make connectivity checking selectable at build-time Just in case you really don't want to install libsoup.
2011-12-05 15:11:13 -06:00
build: unify NetworkManager path handling (some paths are changed) Use autoconf/automake variables for NetworkManager paths. Use NetworkManager subdirectory where appropriate. Files in /var/run (or /run on some distros) are moved into a separate directory as is usual with other daemons. It makes the filesystem more readable and file prefixing unnecessary. /var/run/NetworkManager.pid -> /var/run/NetworkManager/NetworkManager.pid /var/run/nm-dns-dnsmasq.pid -> /var/run/NetworkManager/dnsmasq.pid /var/run/nm-dns-dnsmasq.conf -> /var/run/NetworkManager/dnsmasq.conf The /var/run/NetworkManager directory is created at runtime, if it doesn't exist. Note: Path-based security policies like SELinux and AppArmor may need to be adapted.
2012-08-23 11:53:41 +02:00
if SESSION_TRACKING_CK
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
AM_CPPFLAGS += -DCKDB_PATH=\"${CKDB_PATH}\"
build: unify NetworkManager path handling (some paths are changed) Use autoconf/automake variables for NetworkManager paths. Use NetworkManager subdirectory where appropriate. Files in /var/run (or /run on some distros) are moved into a separate directory as is usual with other daemons. It makes the filesystem more readable and file prefixing unnecessary. /var/run/NetworkManager.pid -> /var/run/NetworkManager/NetworkManager.pid /var/run/nm-dns-dnsmasq.pid -> /var/run/NetworkManager/dnsmasq.pid /var/run/nm-dns-dnsmasq.conf -> /var/run/NetworkManager/dnsmasq.conf The /var/run/NetworkManager directory is created at runtime, if it doesn't exist. Note: Path-based security policies like SELinux and AppArmor may need to be adapted.
2012-08-23 11:53:41 +02:00
endif
build: fix srcdir != builddir
2013-05-08 16:47:48 -04:00
libNetworkManager_la_SOURCES = \
$(nm_sources) \
$(glue_sources)
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
libNetworkManager_la_LIBADD = \
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-core/libnm-core.la \
dhcp: add systemd-based "internal" DHCP client We must also remove -Waggregate-return from m4/compiler-warnings.m4 because systemd uses aggregate return (correctly) in a couple cases, and we cannot keep single-level makefiles and override aggregate-return only for the systemd sub-library. This client currently only supports DHCPv4 because the base systemd code does not yet fully support DHCPv6.
2014-07-22 12:38:20 -05:00
libsystemd-dhcp.la \
build: always link locally-built libraries first (bgo #580131)
2009-08-20 12:31:17 -05:00
$(DBUS_LIBS) \
$(GLIB_LIBS) \
$(GUDEV_LIBS) \
$(LIBNL_LIBS) \
build: clarify systemd-login build flags systemd gets used for more than just systemd-login.
2012-11-06 14:11:05 -06:00
$(SYSTEMD_LOGIN_LIBS) \
core: fix libndp linking We were linking libndp into the NetworkManager binary, but it ought to be marked as a dependency of libNetworkManager, in case a test exercises that code.
2014-07-17 18:04:17 -04:00
$(LIBNDP_LIBS) \
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
$(LIBDL) \
$(LIBM)
2004-11-12 Colin Walters <walters@redhat.com> * configure.in: Strip out TARGET_DISTRO and SYSTEM_BACKEND_FILE variables. Switch to Automake conditionals. * src/Makefile.am (noinst_LTLIBRARIES): Add libnmbackend.la. (libnmbackend_la_SOURCES): Use Automake conditionals to add distro-specific files. * initscript/Makefile.am (SUBDIRS): Update to use conditionals. git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@309 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2004-11-12 18:49:33 +00:00
build: fix linker error for '--disable-concheck' and add '--with-libsoup' When building with '--disable-concheck' with libsoup installed, configure would set HAVE_LIBSOUP. But without connection checking, we didn't link against libsoup, resulting in a linker error. Add a new configure option '--with-libsoup' / '--without-libsoup' to control whether linking against libsoup. The combination '--without-libsoup --enable-concheck' does not make sense. https://bugzilla.gnome.org/show_bug.cgi?id=734062 Signed-off-by: Thomas Haller <thaller@redhat.com>
2014-07-31 20:35:28 +02:00
if WITH_LIBSOUP
core: use non-recursive build Although having different parts of NM in different subdirectories keeps the source tree neat, it has made the build messy, particularly because of cross-dependencies between the subdirs. Reorganize to build all of the pieces of the NetworkManager binary from src/Makefile, and only use recursive make for test programs, helper binaries, and plugins. As part of this, get rid of all the per-directory convenience libraries, and switch to building a single top-level libNetworkManager.la, containing everything except main.c, which all of the test programs can then link against.
2013-05-06 14:18:26 -04:00
libNetworkManager_la_LIBADD += $(LIBSOUP_LIBS)
core: make connectivity checking selectable at build-time Just in case you really don't want to install libsoup.
2011-12-05 15:11:13 -06:00
endif
2006-02-26 Dan Williams <dcbw@redhat.com> * src/Makefile.am - make and install nm-crash-logger * src/nm-logging.[ch] - New files; consolidate logging and crash handling * src/nm-crash-logger.c src/gdb-cmd - Standalong crashlogger for NM, grab a backtrace using GDB * src/NetworkManager.[ch] - Remove signal handling and put it into nm-logging.c git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1499 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-02-27 04:31:52 +00:00
NetworkManager_LDFLAGS = -rdynamic
2006-02-02 Robert Love <rml@novell.com> * src/Makefile.am: If we aren't going to create the run directory at, uh, run-time, create it during install. Then users just doing 'make install' are cool, too. While we are here, create the dispatcher.d directory, too. * src/nm-device-802-11-wireless.c: Let the Makefile define and pass in the exact run directory. * Makefile.am: Install nm-applet.desktop. git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1430 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-02-02 20:52:43 +00:00
dhcp: add systemd-based "internal" DHCP client We must also remove -Waggregate-return from m4/compiler-warnings.m4 because systemd uses aggregate return (correctly) in a couple cases, and we cannot keep single-level makefiles and override aggregate-return only for the systemd sub-library. This client currently only supports DHCPv4 because the base systemd code does not yet fully support DHCPv6.
2014-07-22 12:38:20 -05:00
######################
iface-helper: add nm-iface-helper for dynamic configure-then-quit support When quitting, the Manager asks each device to spawn the interface helper, which persists and manages dynamic address on the interface after NetworkManager is gone. If the dynamic address cannot be maintaned, the helper quits and the interface's address may be removed when their lifetime runs out. To keep the helper as simple as possible, NetworkManager passes most of the configuration on the command-line, including some properties of the device's current state, which are necessary for the helper to maintain DHCP leases or IPv6 SLAAC addresses.
2014-10-29 09:12:18 -05:00
libnm_iface_helper_la_SOURCES = \
dhcp-manager/nm-dhcp-client.c \
dhcp-manager/nm-dhcp-client.h \
dhcp-manager/nm-dhcp-utils.c \
dhcp-manager/nm-dhcp-utils.h \
dhcp-manager/nm-dhcp-manager.c \
dhcp-manager/nm-dhcp-manager.h \
\
platform/nm-linux-platform.c \
platform/nm-linux-platform.h \
platform/nm-platform.c \
platform/nm-platform.h \
platform/wifi/wifi-utils-nl80211.c \
platform/wifi/wifi-utils-nl80211.h \
platform/wifi/wifi-utils-private.h \
platform/wifi/wifi-utils.c \
platform/wifi/wifi-utils.h \
\
rdisc/nm-fake-rdisc.c \
rdisc/nm-fake-rdisc.h \
rdisc/nm-lndp-rdisc.c \
rdisc/nm-lndp-rdisc.h \
rdisc/nm-rdisc.c \
rdisc/nm-rdisc.h \
\
nm-ip4-config.c \
nm-ip4-config.h \
nm-ip6-config.c \
nm-ip6-config.h \
\
nm-enum-types.c \
nm-enum-types.h \
nm-logging.c \
nm-logging.h \
nm-posix-signals.c \
nm-posix-signals.h \
NetworkManagerUtils.c \
NetworkManagerUtils.h
if WITH_WEXT
libnm_iface_helper_la_SOURCES += \
platform/wifi/wifi-utils-wext.c \
platform/wifi/wifi-utils-wext.h
endif
libnm_iface_helper_la_LIBADD = \
$(top_builddir)/libnm-core/libnm-core.la \
libsystemd-dhcp.la \
$(DBUS_LIBS) \
$(GLIB_LIBS) \
$(GUDEV_LIBS) \
$(LIBNL_LIBS) \
$(LIBNDP_LIBS) \
$(LIBDL) \
$(LIBM)
libexec_PROGRAMS = nm-iface-helper
nm_iface_helper_SOURCES = \
dhcp-manager/nm-dhcp-systemd.h \
dhcp-manager/nm-dhcp-systemd.c \
nm-iface-helper.c \
main-utils.c \
main-utils.h
nm_iface_helper_LDADD = \
$(top_builddir)/libnm-core/libnm-core.la \
libsystemd-dhcp.la \
libnm-iface-helper.la \
$(DBUS_LIBS) \
$(GLIB_LIBS) \
$(GUDEV_LIBS) \
$(LIBNL_LIBS) \
$(LIBNDP_LIBS) \
$(LIBM)
nm_iface_helper_LDFLAGS = -rdynamic
######################
removed configure from rep git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@29 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2004-07-28 18:04:23 +00:00
dbusservicedir = $(DBUS_SYS_DIR)
dbus: rename conf file to match current conventions
2011-12-12 19:31:11 -06:00
dbusservice_DATA = org.freedesktop.NetworkManager.conf
Initial revision git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@2 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2004-06-24 14:18:37 +00:00
Revert "core: import libgsystem, use it for local-allocations in main.c (bgo #685440)" This reverts commit 89623b99c44bd7c6b721955ebc0a9550cb8dd978 pending further discussion. See: https://mail.gnome.org/archives/networkmanager-list/2012-October/msg00065.html
2012-10-18 11:53:05 -04:00
EXTRA_DIST = \
2006-03-05 Dan Williams <dcbw@redhat.com> Process netlink messages in device subclasses rather than in NetworkManager.c. Also add support for recognizing Wireless Events. * configure.in - Find GLIB_GENMARSHAL * src/Makefile.am - Since we're marshalling custom types for wireless event signals, we get to create our own marshallers using GLIB_GENMARSHAL * src/NetworkManager.c - (nm_monitor_wired_link_state): renamed to nm_monitor_setup - (nm_monitor_setup): renamed from nm_monitor_wired_link_state, and cut down somewhat. We no longer process signals here. - (nm_data_new): create the netlink monitor here, and remove a useless call to nm_policy_schedule_device_change_check() - (nm_data_free): get rid of the netlink monitor here - (nm_device_link_activated, nm_device_link_deactivated): removed - (main): don't create the netlink monitor here, let nm_data_new do that. Call nm_policy_schedule_device_change_check() right before we jump to the mainloop to figure out which device to use first * src/NetworkManagerSystem.[ch] - (nm_system_get_rtnl_index_from_iface, nm_system_get_iface_from_rtnl_index): convert back and forth from interface names to interface indexes * src/nm-device-802-11-wireless.c - (real_init): connect to wireless-event signals from the netlink monitor object - (nm_device_802_11_wireless_event): new function, schedule handler for wireless event signals from the netlink monitor object. We want the handler to run in the device's context - (wireless_event_helper): handle wireless-event signals from netlink - (nm_device_802_11_wireless_dispose): disconnect wireless-event signal handler * src/nm-device-802-11-wireless.h - remove unused prototype for nm_device_802_11_wireless_new * src/nm-device-802-3-ethernet.c - (real_init): new function; set up signal handlers for link events - (nm_device_802_3_ethernet_link_activated): new function, schedule handler for netlink link activated events on device's main loop - (link_activated_helper): when we get a link activated event, set the device's link to be active - (nm_device_802_3_ethernet_link_deactivated): new function; schedule handler for netlink link deactivated events on device's main loop - (link_deactivated_helper): when we get a link deactivated event, set the device's link to be inactive - (nm_device_802_3_ethernet_dispose): disconnect signal handler on dispose * src/nm-device-802-3-ethernet.h - remove unused prototype for nm_device_802_3_ethernet_new * src/nm-device.[ch] - (nm_get_device_by_iface_locked): variant of nm_get_device_by_iface but locks the device list - (nm_device_set_active_link): a little bit of cleanup and de-indenting * src/nm-netlink-monitor.[ch] - (nm_netlink_monitor_class_install_signals): New signal "wireless-event" - (nm_netlink_monitor_new): keep reference to NMData so we can get at the device list - (nm_netlink_monitor_event_handler): expand for wireless events too * src/nm-marshal-main.c - Include generated nm-marshal.c and nm-marshal.h * src/nm-marshal.list - List of custom marshal functions git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1555 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-03-06 01:10:58 +00:00
$(dbusservice_DATA) \
2007-10-01 Dan Williams <dcbw@redhat.com> * configure.in src/marshallers/Makefile.am src/marshallers/nm-marshal.list src/marshallers/nm-marshal-main.c - Consolidate glib marshallers into one place * src/dhcp-manager/Makefile.am src/dhcp-manager/nm-dhcp-manager.c src/supplicant-manager/Makefile.am src/supplicant-manager/nm-supplicant-manager.c src/supplicant-manager/nm-supplicant-interface.c src/ppp-manager/Makefile.am src/ppp-manager/nm-ppp-manager.c src/vpn-manager/Makefile.am src/vpn-manager/nm-vpn-connection.c src/Makefile.am - Use consolidated marshallers * src/dhcp-manager/nm-dhcp-marshal.list src/dhcp-manager/nm-dhcp-marshal-main.c src/supplicant-manager/nm-supplicant-marshal-main.c src/supplicant-manager/nm-supplicant-marshal.list src/nm-marshal-main.c src/nm-marshal.list src/ppp-manager/nm-ppp-marshal-main.c src/ppp-manager/nm-ppp-marshal.list src/vpn-manager/nm-vpn-marshal-main.c src/vpn-manager/nm-vpn-marshal.list - Remove git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@2920 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2007-10-01 21:26:13 +00:00
$(NetworkManager_DATA)
2006-03-05 Dan Williams <dcbw@redhat.com> Process netlink messages in device subclasses rather than in NetworkManager.c. Also add support for recognizing Wireless Events. * configure.in - Find GLIB_GENMARSHAL * src/Makefile.am - Since we're marshalling custom types for wireless event signals, we get to create our own marshallers using GLIB_GENMARSHAL * src/NetworkManager.c - (nm_monitor_wired_link_state): renamed to nm_monitor_setup - (nm_monitor_setup): renamed from nm_monitor_wired_link_state, and cut down somewhat. We no longer process signals here. - (nm_data_new): create the netlink monitor here, and remove a useless call to nm_policy_schedule_device_change_check() - (nm_data_free): get rid of the netlink monitor here - (nm_device_link_activated, nm_device_link_deactivated): removed - (main): don't create the netlink monitor here, let nm_data_new do that. Call nm_policy_schedule_device_change_check() right before we jump to the mainloop to figure out which device to use first * src/NetworkManagerSystem.[ch] - (nm_system_get_rtnl_index_from_iface, nm_system_get_iface_from_rtnl_index): convert back and forth from interface names to interface indexes * src/nm-device-802-11-wireless.c - (real_init): connect to wireless-event signals from the netlink monitor object - (nm_device_802_11_wireless_event): new function, schedule handler for wireless event signals from the netlink monitor object. We want the handler to run in the device's context - (wireless_event_helper): handle wireless-event signals from netlink - (nm_device_802_11_wireless_dispose): disconnect wireless-event signal handler * src/nm-device-802-11-wireless.h - remove unused prototype for nm_device_802_11_wireless_new * src/nm-device-802-3-ethernet.c - (real_init): new function; set up signal handlers for link events - (nm_device_802_3_ethernet_link_activated): new function, schedule handler for netlink link activated events on device's main loop - (link_activated_helper): when we get a link activated event, set the device's link to be active - (nm_device_802_3_ethernet_link_deactivated): new function; schedule handler for netlink link deactivated events on device's main loop - (link_deactivated_helper): when we get a link deactivated event, set the device's link to be inactive - (nm_device_802_3_ethernet_dispose): disconnect signal handler on dispose * src/nm-device-802-3-ethernet.h - remove unused prototype for nm_device_802_3_ethernet_new * src/nm-device.[ch] - (nm_get_device_by_iface_locked): variant of nm_get_device_by_iface but locks the device list - (nm_device_set_active_link): a little bit of cleanup and de-indenting * src/nm-netlink-monitor.[ch] - (nm_netlink_monitor_class_install_signals): New signal "wireless-event" - (nm_netlink_monitor_new): keep reference to NMData so we can get at the device list - (nm_netlink_monitor_event_handler): expand for wireless events too * src/nm-marshal-main.c - Include generated nm-marshal.c and nm-marshal.h * src/nm-marshal.list - List of custom marshal functions git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1555 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-03-06 01:10:58 +00:00
rundir=$(localstatedir)/run/NetworkManager
build: create NM state directory at install time
2010-11-08 09:09:54 -06:00
statedir=$(localstatedir)/lib/NetworkManager
2006-03-05 Dan Williams <dcbw@redhat.com> Process netlink messages in device subclasses rather than in NetworkManager.c. Also add support for recognizing Wireless Events. * configure.in - Find GLIB_GENMARSHAL * src/Makefile.am - Since we're marshalling custom types for wireless event signals, we get to create our own marshallers using GLIB_GENMARSHAL * src/NetworkManager.c - (nm_monitor_wired_link_state): renamed to nm_monitor_setup - (nm_monitor_setup): renamed from nm_monitor_wired_link_state, and cut down somewhat. We no longer process signals here. - (nm_data_new): create the netlink monitor here, and remove a useless call to nm_policy_schedule_device_change_check() - (nm_data_free): get rid of the netlink monitor here - (nm_device_link_activated, nm_device_link_deactivated): removed - (main): don't create the netlink monitor here, let nm_data_new do that. Call nm_policy_schedule_device_change_check() right before we jump to the mainloop to figure out which device to use first * src/NetworkManagerSystem.[ch] - (nm_system_get_rtnl_index_from_iface, nm_system_get_iface_from_rtnl_index): convert back and forth from interface names to interface indexes * src/nm-device-802-11-wireless.c - (real_init): connect to wireless-event signals from the netlink monitor object - (nm_device_802_11_wireless_event): new function, schedule handler for wireless event signals from the netlink monitor object. We want the handler to run in the device's context - (wireless_event_helper): handle wireless-event signals from netlink - (nm_device_802_11_wireless_dispose): disconnect wireless-event signal handler * src/nm-device-802-11-wireless.h - remove unused prototype for nm_device_802_11_wireless_new * src/nm-device-802-3-ethernet.c - (real_init): new function; set up signal handlers for link events - (nm_device_802_3_ethernet_link_activated): new function, schedule handler for netlink link activated events on device's main loop - (link_activated_helper): when we get a link activated event, set the device's link to be active - (nm_device_802_3_ethernet_link_deactivated): new function; schedule handler for netlink link deactivated events on device's main loop - (link_deactivated_helper): when we get a link deactivated event, set the device's link to be inactive - (nm_device_802_3_ethernet_dispose): disconnect signal handler on dispose * src/nm-device-802-3-ethernet.h - remove unused prototype for nm_device_802_3_ethernet_new * src/nm-device.[ch] - (nm_get_device_by_iface_locked): variant of nm_get_device_by_iface but locks the device list - (nm_device_set_active_link): a little bit of cleanup and de-indenting * src/nm-netlink-monitor.[ch] - (nm_netlink_monitor_class_install_signals): New signal "wireless-event" - (nm_netlink_monitor_new): keep reference to NMData so we can get at the device list - (nm_netlink_monitor_event_handler): expand for wireless events too * src/nm-marshal-main.c - Include generated nm-marshal.c and nm-marshal.h * src/nm-marshal.list - List of custom marshal functions git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1555 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-03-06 01:10:58 +00:00
install-data-hook:
2008-08-17 Dan Williams <dcbw@redhat.com> * callouts/Makefile.am src/Makefile.am - Move dispatcher directory creation to callouts/Makefile.am * system-settings/plugins/keyfile/Makefile.am - Create keyfile connections directory in DESTDIR (bgo #546833) git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3976 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-17 22:54:49 +00:00
$(mkinstalldirs) -m 0700 $(DESTDIR)$(rundir)
build: create NM state directory at install time
2010-11-08 09:09:54 -06:00
$(mkinstalldirs) -m 0700 $(DESTDIR)$(statedir)
build: ensure pkglibdir exists (bgo #688806) Recent automake versions switched to not creating empty directories, but at the moment NetworkManager g_warning()s on startup if it doesn't find $(pkglibdir). So let's make it. https://bugzilla.gnome.org/show_bug.cgi?id=688806
2012-11-20 22:00:46 -05:00
$(mkinstalldirs) -m 0755 $(DESTDIR)$(pkglibdir)
2006-03-05 Dan Williams <dcbw@redhat.com> Process netlink messages in device subclasses rather than in NetworkManager.c. Also add support for recognizing Wireless Events. * configure.in - Find GLIB_GENMARSHAL * src/Makefile.am - Since we're marshalling custom types for wireless event signals, we get to create our own marshallers using GLIB_GENMARSHAL * src/NetworkManager.c - (nm_monitor_wired_link_state): renamed to nm_monitor_setup - (nm_monitor_setup): renamed from nm_monitor_wired_link_state, and cut down somewhat. We no longer process signals here. - (nm_data_new): create the netlink monitor here, and remove a useless call to nm_policy_schedule_device_change_check() - (nm_data_free): get rid of the netlink monitor here - (nm_device_link_activated, nm_device_link_deactivated): removed - (main): don't create the netlink monitor here, let nm_data_new do that. Call nm_policy_schedule_device_change_check() right before we jump to the mainloop to figure out which device to use first * src/NetworkManagerSystem.[ch] - (nm_system_get_rtnl_index_from_iface, nm_system_get_iface_from_rtnl_index): convert back and forth from interface names to interface indexes * src/nm-device-802-11-wireless.c - (real_init): connect to wireless-event signals from the netlink monitor object - (nm_device_802_11_wireless_event): new function, schedule handler for wireless event signals from the netlink monitor object. We want the handler to run in the device's context - (wireless_event_helper): handle wireless-event signals from netlink - (nm_device_802_11_wireless_dispose): disconnect wireless-event signal handler * src/nm-device-802-11-wireless.h - remove unused prototype for nm_device_802_11_wireless_new * src/nm-device-802-3-ethernet.c - (real_init): new function; set up signal handlers for link events - (nm_device_802_3_ethernet_link_activated): new function, schedule handler for netlink link activated events on device's main loop - (link_activated_helper): when we get a link activated event, set the device's link to be active - (nm_device_802_3_ethernet_link_deactivated): new function; schedule handler for netlink link deactivated events on device's main loop - (link_deactivated_helper): when we get a link deactivated event, set the device's link to be inactive - (nm_device_802_3_ethernet_dispose): disconnect signal handler on dispose * src/nm-device-802-3-ethernet.h - remove unused prototype for nm_device_802_3_ethernet_new * src/nm-device.[ch] - (nm_get_device_by_iface_locked): variant of nm_get_device_by_iface but locks the device list - (nm_device_set_active_link): a little bit of cleanup and de-indenting * src/nm-netlink-monitor.[ch] - (nm_netlink_monitor_class_install_signals): New signal "wireless-event" - (nm_netlink_monitor_new): keep reference to NMData so we can get at the device list - (nm_netlink_monitor_event_handler): expand for wireless events too * src/nm-marshal-main.c - Include generated nm-marshal.c and nm-marshal.h * src/nm-marshal.list - List of custom marshal functions git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1555 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-03-06 01:10:58 +00:00
build: clean 0.9.8 generated files Makes it easier to switch between 0.9.8 and git master.
2014-02-26 09:58:15 -06:00
CLEANFILES = \
$(BUILT_SOURCES) \
settings/*-glue.h \
devices/*-glue.h \
devices/*/*-glue.h
2006-03-05 Dan Williams <dcbw@redhat.com> Process netlink messages in device subclasses rather than in NetworkManager.c. Also add support for recognizing Wireless Events. * configure.in - Find GLIB_GENMARSHAL * src/Makefile.am - Since we're marshalling custom types for wireless event signals, we get to create our own marshallers using GLIB_GENMARSHAL * src/NetworkManager.c - (nm_monitor_wired_link_state): renamed to nm_monitor_setup - (nm_monitor_setup): renamed from nm_monitor_wired_link_state, and cut down somewhat. We no longer process signals here. - (nm_data_new): create the netlink monitor here, and remove a useless call to nm_policy_schedule_device_change_check() - (nm_data_free): get rid of the netlink monitor here - (nm_device_link_activated, nm_device_link_deactivated): removed - (main): don't create the netlink monitor here, let nm_data_new do that. Call nm_policy_schedule_device_change_check() right before we jump to the mainloop to figure out which device to use first * src/NetworkManagerSystem.[ch] - (nm_system_get_rtnl_index_from_iface, nm_system_get_iface_from_rtnl_index): convert back and forth from interface names to interface indexes * src/nm-device-802-11-wireless.c - (real_init): connect to wireless-event signals from the netlink monitor object - (nm_device_802_11_wireless_event): new function, schedule handler for wireless event signals from the netlink monitor object. We want the handler to run in the device's context - (wireless_event_helper): handle wireless-event signals from netlink - (nm_device_802_11_wireless_dispose): disconnect wireless-event signal handler * src/nm-device-802-11-wireless.h - remove unused prototype for nm_device_802_11_wireless_new * src/nm-device-802-3-ethernet.c - (real_init): new function; set up signal handlers for link events - (nm_device_802_3_ethernet_link_activated): new function, schedule handler for netlink link activated events on device's main loop - (link_activated_helper): when we get a link activated event, set the device's link to be active - (nm_device_802_3_ethernet_link_deactivated): new function; schedule handler for netlink link deactivated events on device's main loop - (link_deactivated_helper): when we get a link deactivated event, set the device's link to be inactive - (nm_device_802_3_ethernet_dispose): disconnect signal handler on dispose * src/nm-device-802-3-ethernet.h - remove unused prototype for nm_device_802_3_ethernet_new * src/nm-device.[ch] - (nm_get_device_by_iface_locked): variant of nm_get_device_by_iface but locks the device list - (nm_device_set_active_link): a little bit of cleanup and de-indenting * src/nm-netlink-monitor.[ch] - (nm_netlink_monitor_class_install_signals): New signal "wireless-event" - (nm_netlink_monitor_new): keep reference to NMData so we can get at the device list - (nm_netlink_monitor_event_handler): expand for wireless events too * src/nm-marshal-main.c - Include generated nm-marshal.c and nm-marshal.h * src/nm-marshal.list - List of custom marshal functions git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@1555 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2006-03-06 01:10:58 +00:00
Reference in a new issue Copy permalink