NetworkManager/cli/src/Makefile.am

bin_PROGRAMS = \
	nmcli

AM_CPPFLAGS = \
	-I${top_srcdir} \
	-I${top_srcdir}/include \
	-I${top_builddir}/include \
	-I${top_srcdir}/libnm-util \
	-I${top_builddir}/libnm-util \
	-I${top_srcdir}/libnm-glib \
	$(DBUS_CFLAGS) \
	$(GLIB_CFLAGS) \
	-DG_LOG_DOMAIN=\""nmcli"\" \
	-DNM_VERSION_MAX_ALLOWED=NM_VERSION_NEXT_STABLE \
	-DNMCLI_LOCALEDIR=\"$(datadir)/locale\"

nmcli_SOURCES = \
	common.c \
	common.h \
	connections.c \
	connections.h \
	devices.c \
	devices.h \
	network-manager.c \
	network-manager.h \
	settings.c \
	settings.h \
	nmcli.c \
	nmcli.h \
	utils.c \
	utils.h

nmcli_LDADD = \
	$(DBUS_LIBS) \
	$(GLIB_LIBS) \
	$(READLINE_LIBS) \
	$(top_builddir)/libnm-util/libnm-util.la \
	$(top_builddir)/libnm-glib/libnm-glib.la
cli: add initial pieces of nmcli 2010-02-25 09:52:30 -08:00			`bin_PROGRAMS = \`
			`nmcli`

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 = \`
cli: add initial pieces of nmcli 2010-02-25 09:52:30 -08:00			`-I${top_srcdir} \`
			`-I${top_srcdir}/include \`
build: fix srcdir != builddir nm-version.h is in ${top_builddir}/include. 2012-01-08 12:30:02 -05:00			`-I${top_builddir}/include \`
cli: add initial pieces of nmcli 2010-02-25 09:52:30 -08:00			`-I${top_srcdir}/libnm-util \`
build: fix srcdir != builddir for new generated headers 2012-02-22 16:37:38 -05:00			`-I${top_builddir}/libnm-util \`
build: switch from $(INCLUDES) to $(AM_CPPFLAGS) to make automake happy Unfortunately, $(AM_CPPFLAGS) gets overridden by per-target _CPPFLAGS variables, which $(INCLUDES) did not, so this requires some additional changes. In most places, I have just gotten rid of the per-target _CPPFLAGS variables; in directories with a single target, the per-target variable is unnecessary, and in directories with multiple targets, the per-target variable is often undesirable, since it forces some files to be compiled twice, even though there ends up being no difference between the two files. 2013-08-22 10:47:21 -04:00			`-I${top_srcdir}/libnm-glib \`
			`$(DBUS_CFLAGS) \`
			`$(GLIB_CFLAGS) \`
all: set G_LOG_DOMAIN appropriately, for better g_log() messages 2014-04-07 16:14:47 -04:00			`-DG_LOG_DOMAIN=\""nmcli"\" \`
libnm-util, libnm-glib: add versioned deprecation/availability macros Add versioned NM_DEPRECATED_IN_* and NM_AVAILABLE_IN_* macros, and tag new/deprecated functions accordingly. (All currently-deprecated functions are assumed to have been deprecated in 0.9.10.) Add NM_VERSION_MIN_REQUIRED and NM_VERSION_MAX_ALLOWED macros which can be set to determine which versions will cause warnings. With the current settings, external consumers of the libnm-util/libnm-glib APIs will have MIN_REQUIRED and MAX_ALLOWED both set to NM_VERSION_0_9_8 by default, meaning they will get warnings about functions added in 0.9.10. NM internally sets NM_VERSION_MAX_ALLOWED to NM_VERSION_NEXT_STABLE to ensure that it is always allowed to use all APIs. 2014-02-12 12:28:52 -05:00			`-DNM_VERSION_MAX_ALLOWED=NM_VERSION_NEXT_STABLE \`
build: switch from $(INCLUDES) to $(AM_CPPFLAGS) to make automake happy Unfortunately, $(AM_CPPFLAGS) gets overridden by per-target _CPPFLAGS variables, which $(INCLUDES) did not, so this requires some additional changes. In most places, I have just gotten rid of the per-target _CPPFLAGS variables; in directories with a single target, the per-target variable is unnecessary, and in directories with multiple targets, the per-target variable is often undesirable, since it forces some files to be compiled twice, even though there ends up being no difference between the two files. 2013-08-22 10:47:21 -04:00			`-DNMCLI_LOCALEDIR=\"$(datadir)/locale\"`
cli: add initial pieces of nmcli 2010-02-25 09:52:30 -08:00
			`nmcli_SOURCES = \`
cli: move IP config printing code from devices.c to common.c That allows sharing the code between devices and active connections. 2012-01-06 13:51:33 +01:00			`common.c \`
			`common.h \`
cli: add initial pieces of nmcli 2010-02-25 09:52:30 -08:00			`connections.c \`
			`connections.h \`
			`devices.c \`
			`devices.h \`
			`network-manager.c \`
			`network-manager.h \`
cli: use own code to output connection details (settings) nmcli uses its own code to dump connections' details instead of libnm-util's nm_connection_dump(). It allows to structure output and present values of the settings according to nmcli needs. 2010-03-31 17:14:35 +02:00			`settings.c \`
			`settings.h \`
cli: add initial pieces of nmcli 2010-02-25 09:52:30 -08:00			`nmcli.c \`
			`nmcli.h \`
			`utils.c \`
			`utils.h`

			`nmcli_LDADD = \`
			`$(DBUS_LIBS) \`
			`$(GLIB_LIBS) \`
cli/build: make libreadline a build-time dependency (bgo #729846) and link nmcli against it. This simplifies code, makes sure that line editing capability is supported, and will allow using readline on other places too. https://bugzilla.gnome.org/show_bug.cgi?id=729846 https://bugzilla.redhat.com/show_bug.cgi?id=1007365 2014-05-13 15:50:38 +02:00			`$(READLINE_LIBS) \`
cli: add initial pieces of nmcli 2010-02-25 09:52:30 -08:00			`$(top_builddir)/libnm-util/libnm-util.la \`
			`$(top_builddir)/libnm-glib/libnm-glib.la`