fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2026-01-19 02:10:31 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/src/settings/plugins/example/Makefile.am

40 lines
1.1 KiB
Text
Raw Normal View History

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 = \
settings: port NMAgentManager, etc, to use NMAuthSubject Rather than explicitly passing around a UID and a flag saying whether or not it's relevant. (This also fixes a bug where the wrong UID was being recorded in nm-settings-connection.c::auth_start(), which caused problems such as agent-owned secrets not getting saved because of a perceived UID mismatch.)
2013-11-05 14:36:38 -05:00
-I$(top_srcdir)/src \
settings: don't pass config_path to NMSettings and settings plugins They can just call nm_config_get() now to get the config, and nm_config_get_path() to get its path.
2013-03-12 11:11:54 -04:00
-I$(top_srcdir)/src/config \
examples: add an example system settings plugin
2012-05-07 15:19:09 -05:00
-I$(top_srcdir)/src/settings \
-I$(top_srcdir)/include \
-I$(top_builddir)/include \
-I$(top_srcdir)/libnm-util \
build: switch from $(INCLUDES) to $(AM_CPPFLAGS) to make automake happy Unfortunately, $(AM_CPPFLAGS) gets overridden by per-target _CPPFLAGS variables, which $(INCLUDES) did not, so this requires some additional changes. In most places, I have just gotten rid of the per-target _CPPFLAGS variables; in directories with a single target, the per-target variable is unnecessary, and in directories with multiple targets, the per-target variable is often undesirable, since it forces some files to be compiled twice, even though there ends up being no difference between the two files.
2013-08-22 10:47:21 -04:00
-I$(top_builddir)/libnm-util \
all: set G_LOG_DOMAIN appropriately, for better g_log() messages
2014-04-07 16:14:47 -04:00
-DG_LOG_DOMAIN=\""NetworkManager-example"\" \
libnm-util, libnm-glib: add versioned deprecation/availability macros Add versioned NM_DEPRECATED_IN_* and NM_AVAILABLE_IN_* macros, and tag new/deprecated functions accordingly. (All currently-deprecated functions are assumed to have been deprecated in 0.9.10.) Add NM_VERSION_MIN_REQUIRED and NM_VERSION_MAX_ALLOWED macros which can be set to determine which versions will cause warnings. With the current settings, external consumers of the libnm-util/libnm-glib APIs will have MIN_REQUIRED and MAX_ALLOWED both set to NM_VERSION_0_9_8 by default, meaning they will get warnings about functions added in 0.9.10. NM internally sets NM_VERSION_MAX_ALLOWED to NM_VERSION_NEXT_STABLE to ensure that it is always allowed to use all APIs.
2014-02-12 12:28:52 -05:00
-DNM_VERSION_MAX_ALLOWED=NM_VERSION_NEXT_STABLE \
build: switch from $(INCLUDES) to $(AM_CPPFLAGS) to make automake happy Unfortunately, $(AM_CPPFLAGS) gets overridden by per-target _CPPFLAGS variables, which $(INCLUDES) did not, so this requires some additional changes. In most places, I have just gotten rid of the per-target _CPPFLAGS variables; in directories with a single target, the per-target variable is unnecessary, and in directories with multiple targets, the per-target variable is often undesirable, since it forces some files to be compiled twice, even though there ends up being no difference between the two files.
2013-08-22 10:47:21 -04:00
$(GLIB_CFLAGS) \
$(DBUS_CFLAGS) \
settings: port NMAgentManager, etc, to use NMAuthSubject Rather than explicitly passing around a UID and a flag saying whether or not it's relevant. (This also fixes a bug where the wrong UID was being recorded in nm-settings-connection.c::auth_start(), which caused problems such as agent-owned secrets not getting saved because of a perceived UID mismatch.)
2013-11-05 14:36:38 -05:00
$(POLKIT_CFLAGS) \
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
-DNMCONFDIR=\"$(nmconfdir)\"
examples: add an example system settings plugin
2012-05-07 15:19:09 -05:00
# 'noinst' here because this is an example plugin we don't want to install
noinst_LTLIBRARIES = libnm-settings-plugin-example.la
# The actual plugins typically pull reader.c and writer.c out into
# their own static library so that unit tests can use them without
# having to build the entire plugin. But since this is a simple
# plugin we don't do that yet.
libnm_settings_plugin_example_la_SOURCES = \
nm-example-connection.c \
nm-example-connection.h \
plugin.c \
plugin.h \
errors.c \
common.h \
reader.c \
writer.c
libnm_settings_plugin_example_la_LIBADD = \
$(top_builddir)/libnm-util/libnm-util.la \
build: clean up GLib-related pkg-config usage (bgo #687218) We had separate checks for glib-2.0, gobject-2.0, gmodule-2.0, and gio-unix-2.0. It doesn't make sense to link a binary against all 4 because gio-unix-2.0 depends on glib-2.0 and gobject-2.0. Doing this actually breaks things in unusual circumstances. Generally, few bits of NM actually just use glib, and not gio. We might as well coalesce those requirements together, even if it means in some cases we "overlink". Additionally, I chose for now to fold gmodule-2.0 in as well, even though many fewer programs need it. The cost of overlinking is quite small. The benefit of this is less repeated junk in Makefile.am, as well as more centralized control over GLib. A followup patch will allow us to set -DGLIB_VERSION_MIN_REQUIRED in just one place, rather than having to replicate it 4 times. The NM configure is still suboptimal - for example, libpolkit-1 depends on gio-2.0, so really we should determine the compiler flags all in one pass. But it doesn't matter too much for now.
2012-10-31 20:21:32 +01:00
$(GLIB_LIBS)
examples: add an example system settings plugin
2012-05-07 15:19:09 -05:00
settings: fix example plugin LDFLAGS C&P error.
2012-05-14 15:51:31 -05:00
libnm_settings_plugin_example_la_LDFLAGS = -module -avoid-version
examples: add an example system settings plugin
2012-05-07 15:19:09 -05:00
Reference in a new issue Copy permalink