Commit e4fda00d authored by Carsten Munk's avatar Carsten Munk

Squashed 'connman/' content from commit eda292c

git-subtree-dir: connman
git-subtree-split: eda292ce0c92f6e866474ea72b3fea7a1b37029b
parents
*.o
*.a
*.lo
*.la
.deps
.libs
.dirstamp
Makefile
Makefile.in
aclocal.m4
config.guess
config.h
config.h.in
config.log
config.status
config.sub
configure
depcomp
compile
install-sh
libtool
ltmain.sh
missing
stamp-h1
autom4te.cache
connman.pc
include/connman
include/version.h
src/builtin.h
src/connmand
src/connman.conf
src/connman.service
src/*-connman.rules
plugins/connman.policy
scripts/connman
scripts/openconnect-script
scripts/openvpn-script
client/connmanctl
tools/wispr
tools/dhcp-test
tools/dhcp-server-test
tools/addr-test
tools/tap-test
tools/web-test
tools/wpad-test
tools/resolv-test
tools/polkit-test
tools/iptables-test
tools/iptables-unit
tools/dnsproxy-test
tools/supplicant-test
tools/dbus-test
tools/stats-tool
tools/stats-ringbuffer-dump
tools/private-network-test
tools/session-test
unit/test-ippool
unit/test-nat
unit/test-pbkdf2-sha1
unit/test-prf-sha1
doc/*.bak
doc/*.stamp
doc/connman.*
!doc/connman.8
!doc/connman.conf.5
doc/connman-*.txt
doc/*.sgml
doc/version.xml
doc/xml
doc/html
vpn/builtin.h
vpn/connman-vpnd
vpn/connman-vpn.service
vpn/net.connman.vpn.service
Luiz Augusto von Dentz <luiz.dentz-von@nokia.com> <luiz.dentz-von@nokia.com>
Leena Gunda <leena.gunda@wipro.com> <leena.gunda@wipro.com>
Flávio Ceolin <flavio.ceolin@profusion.mobi> <flavio.ceolin@profusion.mobi>
Daniel Wagner <daniel.wagner@bmw-carit.de> <daniel.wagner@bmw-carit.de>
Marcel Holtmann <marcel@holtmann.org>
Inaky Perez-Gonzalez <inaky@linux.intel.com>
Samuel Ortiz <sameo@linux.intel.com>
Joshua Lock <josh@linux.intel.com>
Richard Purdie <rpurdie@linux.intel.com>
Gustavo Sverzut Barbieri <barbieri@profusion.mobi>
Martin Xu <martin.xu@intel.com>
Sam Leffler <sleffler@google.com>
Daniel Wagner <daniel.wagner@bmw-carit.de>
Forest Bond <forest@alittletooquiet.net>
Kalle Valo <kalle.valo@canonical.com>
Fabien Marotte <fabienx.marotte@linux.intel.com>
Pekka Pessi <pekka.pessi@nokia.com>
Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Cristiano Fernandes <cristiano.fernandes@hp.com>
Joey Lee <jlee@novell.com>
Leena Gunda <leena.gunda@wipro.com>
Patrik Flykt <patrik.flykt@linux.intel.com>
David Woodhouse <dwmw2@infradead.org>
Gustavo Padovan <gustavo@padovan.org>
Julien Massot <jmassot@aldebaran-robotics.com>
Jukka Rissanen <jukka.rissanen@linux.intel.com>
Grant Erickson <marathon96@gmail.com>
Guillaume Lucas <guillaumex.lucas@intel.com>
Henri Bragge <henri.bragge@ixonos.com>
Alok Barsode <alok.barsode@intel.com>
Sébastien Bianti <sebastien.bianti@linux.intel.com>
Yu A Wang <yu.a.wang@intel.com>
Thierry Boureille <thierry.boureille@gmail.com>
Paolo Pellegrino <paolo.pellegrino@zirak.it>
Bertrand Aygon <bertrand.aygon@intel.com>
Jeff Zheng <jeff.zheng@intel.com>
Philippe Nunes <philippe.nunes@linux.intel.com>
Danny Jeongseok Seo <s.seo@samsung.com>
Flávio Ceolin <flavio.ceolin@profusion.mobi>
Arjan van de Ven <arjan@linux.intel.com>
Daniel Mack <zonque@gmail.com>
Guillaume Zajac <guillaume.zajac@linux.intel.com>
Manfred Kober <manfred.kober@gmx.de>
Mario Domenech Goulart <mario.goulart@gmail.com>
Otavio Salvador <otavio@ossystems.com.br>
Tim Sander <tim01@iss.tu-darmstadt.de>
Adrien Bustany <adrien.bustany@nokia.com>
Henrique Dante de Almeida <hdante@profusion.mobi>
Lucas De Marchi <lucas.demarchi@profusion.mobi>
Elena Tebesoi <elena.tebesoi@gmail.com>
Mikel Astiz <mikel.astiz@bmw-carit.de>
Paulo Pizarro <paulo.pizarro@gmail.com>
Ross Burton <ross.burton@intel.com>
Tudor Marcu <tudor.a.marcu@intel.com>
Ceara Chewning <ceara.k.chewning@intel.com>
Johannes Berg <johannes.berg@intel.com>
Justin Maggard <jmaggard10@gmail.com>
Yann E. Morin <yann.morin.1998@free.fr>
This diff is collapsed.
This diff is collapsed.
Hacking on Connection Manager
*****************************
Build tools requirements
========================
When building and testing directly from the repository it is important to
have at least automake version 1.10 or later installed. All modern
distributions should default to the latest version, but it seems that
Debian's default is still an earlier version:
Check version
# dpkg -l '*automake*'
Install new version
# apt-get install automake1.10
# update-alternatives --config automake
Working with the source code repository
=======================================
The repository contains two extra scripts that accomplish the bootstrap
process. One is called "bootstrap" which is the basic scripts that uses the
autotools scripts to create the needed files for building and installing.
It makes sure to call the right programs depending on the usage of shared or
static libraries or translations etc.
The second program is called "bootstrap-configure". This program will make
sure to properly clean the repository, call the "bootstrap" script and then
call configure with proper settings for development. It will use the best
options and pass them over to configure. These options normally include
the enabling the maintainer mode and the debugging features.
So while in a normal source project the call "./configure ..." is used to
configure the project with its settings like prefix and extra options. In
case of bare repositories call "./bootstrap-configure" and it will bootstrap
the repository and calls configure with all the correct options to make
development easier.
In case of preparing for a release with "make distcheck", don't use
bootstrap-configure since it could export development specific settings.
So the normal steps to checkout, build and install such a repository is
like this:
Checkout repository
# git clone git://git.kernel.org/pub/scm/network/connman/connman.git
# cd connman
Configure and build
# ./bootstrap-configure
# make
Check installation
# make install DESTDIR=$PWD/x
# find x
# rm -rf x
Check distribution
# make distcheck
Final installation
# sudo make install
Remove autogenerated files
# make maintainer-clean
Running from within the source code repository
==============================================
When using "./configure --enable-maintainer-mode" the automake scripts will
use the plugins directly from within the repository. This removes the need
to use "make install" when testing "connmand". The "bootstrap-configure"
automatically includes this option.
Run daemon in foreground with debugging
# sudo ./src/connmand -n -d 'plugins/*'
The debugging option -d takes an argument. This argument can be a comma
separated list of file names like 'plugins/wifi.c,plugins/ethernet.c' to
enable debugs in these files. Simple glob style pattern matching is
supported in this list.
For production installations or distribution packaging it is important that
the "--enable-maintainer-mode" option is NOT used.
Some times it is important to restrict the available interfaces. For example
in cases where testing happens over a network connection. The "-i" command
line switch allows to specify a glob pattern for the interface names.
Run daemon for wireless interfaces
# sudo ./src/connmand -n -i wlan*
Debugging the D-Bus interface during runtime
============================================
Running the daemon with debugging information in the foreground is quite
verbose and sometimes not really helpful. The "monitor-connman" script
allows to monitor "PropertyChanged" D-Bus signals from various interfaces.
Every "PropertyChanged" signal will generate a line of output. Some of them
can get very complex. The first detail inside "{ ... }" is the interface
name (without its service name prefix). The second detail inside "[ ... ]"
is the object path. And after that it is followed by a key and value of
the property that changed.
Generating source code documentation
====================================
The source code is annotated using the gtk-doc style documentation. This
allows an easy way of generating API documentation. The "bootstrap-configure"
script will use the "--enable-gtk-doc" configure to enable the generation of
the documentation.
To make the gtk-doc process work, the gtk-doc tools need to be installed.
Every distribution should provide a package for this, but the naming of the
package might be different:
Debian
# apt-get install gtk-doc-tools
Ubuntu
# apt-get install gtk-doc-utils
Fedora
# yum install gtk-doc
In case "bootstrap-configure" is not used, the manual steps for generating
the documentation files are like this:
Configuring the repository
# ./configure --enable-gtk-doc
Generate the documentation
# cd doc && make
View documentation
# firefox doc/html/index.html
Installation Instructions
*************************
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'. You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that the
`configure' script does not know about. Run `./configure --help' for
details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PREFIX', the package will
use PREFIX as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
CPU-COMPANY-SYSTEM
where SYSTEM can have one of these forms:
OS KERNEL-OS
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
==================
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script). Here is a another example:
/bin/bash ./configure CONFIG_SHELL=/bin/bash
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.
`configure' Invocation
======================
`configure' recognizes the following options to control how it operates.
`--help'
`-h'
Print a summary of the options to `configure', and exit.
`--version'
`-V'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`--cache-file=FILE'
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
`--config-cache'
`-C'
Alias for `--cache-file=config.cache'.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
This diff is collapsed.
plugin_cflags = -fvisibility=hidden -I$(srcdir)/gdbus \
@DBUS_CFLAGS@ @GLIB_CFLAGS@
plugin_ldflags = -no-undefined -module -avoid-version
script_cflags = -fvisibility=hidden -I$(srcdir)/gdbus \
@DBUS_CFLAGS@
if LOOPBACK
builtin_modules += loopback
builtin_sources += plugins/loopback.c
endif
if ETHERNET
builtin_modules += ethernet
builtin_sources += plugins/ethernet.c
endif
gsupplicant_sources = gsupplicant/gsupplicant.h gsupplicant/dbus.h \
gsupplicant/supplicant.c gsupplicant/dbus.c
if WIFI
builtin_modules += wifi
builtin_sources += plugins/wifi.c $(gsupplicant_sources)
endif
if BLUETOOTH
builtin_modules += bluetooth_legacy
builtin_sources += plugins/bluetooth_legacy.c
builtin_modules += bluetooth
builtin_sources += plugins/bluetooth.c
endif
if HH2SERIAL_GPS
if HH2SERIAL_GPS_BUILTIN
builtin_modules += hh2serial_gps
builtin_sources += plugins/hh2serial-gps.c
else
plugin_LTLIBRARIES += plugins/hh2serial-gps.la
plugin_objects += $(plugins_hh2serial_gps_la_OBJECTS)
plugins_hh2serial_gps_la_CFLAGS = $(plugin_cflags)
plugins_hh2serial_gps_la_LDFLAGS = $(plugin_ldflags)
endif
endif
if OFONO
builtin_modules += ofono
builtin_sources += plugins/mcc.h plugins/ofono.c
endif
if DUNDEE
builtin_modules += dundee
builtin_sources += plugins/dundee.c
endif
if VPN
builtin_modules += vpn
builtin_sources += plugins/vpn.c
if OPENCONNECT
if OPENCONNECT_BUILTIN
builtin_vpn_modules += openconnect
builtin_vpn_sources += vpn/plugins/openconnect.c
builtin_vpn_source = vpn/plugins/vpn.c vpn/plugins/vpn.h
builtin_vpn_cflags += -DOPENCONNECT=\"@OPENCONNECT@\"
else
vpn_plugin_LTLIBRARIES += vpn/plugins/openconnect.la
vpn_plugin_objects += $(plugins_openconnect_la_OBJECTS)
vpn_plugins_openconnect_la_SOURCES = vpn/plugins/vpn.h vpn/plugins/vpn.c \
vpn/plugins/openconnect.c
vpn_plugins_openconnect_la_CFLAGS = $(plugin_cflags) \
-DOPENCONNECT=\"@OPENCONNECT@\" \
-DSTATEDIR=\""$(statedir)"\" \
-DSCRIPTDIR=\""$(build_scriptdir)"\"
vpn_plugins_openconnect_la_LDFLAGS = $(plugin_ldflags)
endif
endif
if OPENVPN
if OPENVPN_BUILTIN
builtin_vpn_modules += openvpn
builtin_vpn_sources += vpn/plugins/openvpn.c
builtin_vpn_source = vpn/plugins/vpn.c vpn/plugins/vpn.h
builtin_vpn_cflags += -DOPENVPN=\"@OPENVPN@\"
else
vpn_plugin_LTLIBRARIES += vpn/plugins/openvpn.la
vpn_plugin_objects += $(plugins_openvpn_la_OBJECTS)
vpn_plugins_openvpn_la_SOURCES = vpn/plugins/vpn.h vpn/plugins/vpn.c \
vpn/plugins/openvpn.c
vpn_plugins_openvpn_la_CFLAGS = $(plugin_cflags) -DOPENVPN=\"@OPENVPN@\" \
-DSTATEDIR=\""$(statedir)"\" \
-DSCRIPTDIR=\""$(build_scriptdir)"\"
vpn_plugins_openvpn_la_LDFLAGS = $(plugin_ldflags)
endif
endif
if VPNC
if VPNC_BUILTIN
builtin_vpn_modules += vpnc
builtin_vpn_sources += vpn/plugins/vpnc.c
builtin_vpn_source = vpn/plugins/vpn.c vpn/plugins/vpn.h
builtin_vpn_cflags += -DVPNC=\"@VPNC@\"
else
vpn_plugin_LTLIBRARIES += vpn/plugins/vpnc.la
vpn_plugin_objects += $(plugins_vpnc_la_OBJECTS)
vpn_plugins_vpnc_la_SOURCES = vpn/plugins/vpn.h vpn/plugins/vpn.c \
vpn/plugins/vpnc.c
vpn_plugins_vpnc_la_CFLAGS = $(plugin_cflags) -DVPNC=\"@VPNC@\" \
-DSTATEDIR=\""$(statedir)"\" \