Dan Winship c4417c71b6 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-08 15:07:18 -04:00
..
nm-bluez-adapter.c	bluetooth: move device logic to bluez manager	2012-05-17 13:27:09 -05:00
nm-bluez-adapter.h	core: fix NM_IS_*_CLASS(klass) macros	2012-07-27 13:15:54 +02:00
nm-bluez-common.h	bluetooth: ask Bluez to connect/disconnect from remote device when appropriate	2009-05-14 19:17:56 -04:00
nm-bluez-device.c	libnm-glib, core: use g_cclosure_marshal_generic	2013-05-08 14:59:29 -04:00
nm-bluez-device.h	core: fix NM_IS_*_CLASS(klass) macros	2012-07-27 13:15:54 +02:00
nm-bluez-manager.c	libnm-glib, core: use g_cclosure_marshal_generic	2013-05-08 14:59:29 -04:00
nm-bluez-manager.h	core: fix NM_IS_*_CLASS(klass) macros	2012-07-27 13:15:54 +02:00