Commit e3d550a3 authored by Samuel Thibault's avatar Samuel Thibault

Import Upstream version 0.8.14

parents
This diff is collapsed.
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' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', 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
pass the option `--exec-prefix=PREFIX' to `configure', the package uses
PREFIX as the prefix for installing programs and libraries.
Documentation and other data files 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 option `--target=TYPE' 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.
This diff is collapsed.
ACLOCAL_AMFLAGS = -I m4 ${ACLOCAL_FLAGS}
ALL_SUBDIRS = \
include \
src \
backend \
plugin \
metadata \
config
SUBDIRS = $(ALL_SUBDIRS)
EXTRA_DIST = \
AUTHORS \
COPYING \
LICENSE.GPL \
LICENSE.LGPL \
NEWS \
README.md \
autogen.sh \
libcompizconfig.pc.in
clean:
for sdir in $(SUBDIRS) ; do \
cd $$sdir; make clean; cd .. ; \
done
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = libcompizconfig.pc
# Build ChangeLog from GIT history
ChangeLog:
$(AM_V_GEN) if test -d $(top_srcdir)/.git; then \
GIT_DIR="$(top_srcdir)/.git" git log --stat > $@; \
fi
dist: ChangeLog
.PHONY: ChangeLog
Release 0.8.14 (2017-04-18 Scott Moreau <oreaus@gmail.com>)
==================================================================
COMPIZ-RELOADED
Maintenance release.
Release 0.8.12.1 (2016-04-10 Sorokin Alexei <sor.alexei@meowr.ru>)
==================================================================
COMPIZ-RELOADED
Include autogen.sh into the tarball.
Drop locales support which is without actual locales.
Release 0.8.12 (2016-02-12 Sorokin Alexei <sor.alexei@meowr.ru>)
================================================================
COMPIZ-RELOADED
Avoid using templates in C code.
Release 0.8.9 (2015-11-06 Wolfgang Ulbrich <chat-to-me@raveit.de>)
==================================================================
COMPIZ-RELOADED
Accept <Primary> as <Control>.
MATE support.
Do not use GConf in any session.
# libcompizconfig
Futher development of Compiz 0.8.x series (compiz-reloaded).
CompizConfig plugin required for compizconfig-settings-manager.
- write a simple ini file implementation to read/write general options without
glib (maybe for inport/export of setting too)
- python bindings (and beryl-settings then)
- port ini, gconf backend
- settings plugin
#!/bin/sh
# Run this to generate all the initial makefiles, etc.
srcdir=$(dirname "$0")
[ -z "$srcdir" ] && srcdir="."
cd "$srcdir"
PKG_NAME="libcompizconfig"
if [ ! -f "$srcdir/configure.ac" ]; then
echo -n "**Error**: Directory "\`"$srcdir"\'" does not look like the"
echo " top-level $PKG_NAME directory"
exit 1
fi
autoreconf --verbose --force --install || exit 1
cd "$OLDPWD" || exit $?
if [ -z "$NOCONFIGURE" ]; then
"$srcdir/configure" "$@" || exit 1
fi
## Process this file with automake to produce Makefile.in
AM_CPPFLAGS = \
@COMPIZ_CFLAGS@ \
-I$(top_srcdir)/include \
-I$(top_srcdir)/src \
-DPLUGINDIR=\"$(PLUGINDIR)\" \
-DLIBDIR=\"$(libdir)\"
libini_la_LDFLAGS = -module -avoid-version -no-undefined $(all_libraries)
libini_la_LIBADD = $(top_builddir)/src/libcompizconfig.la
libini_la_SOURCES = ini.c
backenddir = $(libdir)/compizconfig/backends
METASOURCES = AUTO
backend_LTLIBRARIES = libini.la
This diff is collapsed.
globalconfigdir = $(sysconfdir)/compizconfig
globalconfig_DATA = \
config
EXTRA_DIST = \
config
\ No newline at end of file
[general]
backend = ini
plugin_list_autosort = true
AC_PREREQ(2.57)
AC_INIT([libcompizconfig], [0.8.14], [chat-to-me@raveit.de])
AM_INIT_AUTOMAKE([1.9 foreign tar-ustar dist-xz no-dist-gzip check-news])
AC_PROG_CXX
AC_CONFIG_HEADER([config.h])
AM_MAINTAINER_MODE
AC_ISC_POSIX
AC_PROG_CC
AC_PROG_CPP
LT_INIT
AC_HEADER_STDC
AC_CHECK_HEADERS([stdlib.h sys/time.h unistd.h])
AC_CONFIG_MACRO_DIR([m4])
if test "x$GCC" = "xyes"; then
case " $CFLAGS " in
*[[\ \ ]]-Wall[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -Wall" ;;
esac
case " $CFLAGS " in
*[[\ \ ]]-Wpointer-arith[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -Wpointer-arith" ;;
esac
case " $CFLAGS " in
*[[\ \ ]]-Wstrict-prototypes[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -Wstrict-prototypes" ;;
esac
case " $CFLAGS " in
*[[\ \ ]]-Wmissing-prototypes[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -Wmissing-prototypes" ;;
esac
case " $CFLAGS " in
*[[\ \ ]]-Wmissing-declarations[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -Wmissing-declarations" ;;
esac
case " $CFLAGS " in
*[[\ \ ]]-Wnested-externs[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -Wnested-externs" ;;
esac
case " $CFLAGS " in
*[[\ \ ]]-fno-strict-aliasing[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -fno-strict-aliasing" ;;
esac
if test "x$enable_ansi" = "xyes"; then
case " $CFLAGS " in
*[[\ \ ]]-ansi[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -ansi" ;;
esac
case " $CFLAGS " in
*[[\ \ ]]-pedantic[[\ \ ]]*) ;;
*) CFLAGS="$CFLAGS -pedantic" ;;
esac
fi
fi
AC_C_BIGENDIAN
PKG_CHECK_MODULES(LIBX11, "x11")
PKG_CHECK_MODULES(COMPIZ, "compiz")
if test -z "$PKG_CONFIG"; then
AC_PATH_PROG(PKG_CONFIG, pkg-config, no)
fi
if test "$PKG_CONFIG" != "no" ; then
PLUGINDIR=`$PKG_CONFIG --variable=libdir compiz`/compiz
AC_SUBST(PLUGINDIR)
METADATADIR=`$PKG_CONFIG --variable=prefix compiz`/share/compiz
AC_SUBST(METADATADIR)
fi
plugindir=$libdir/compiz
AC_SUBST(plugindir)
PKG_CHECK_MODULES(LIBXML2, "libxml-2.0")
AC_SUBST(LIBXML2_REQUIRES)
AC_ARG_ENABLE(protobuf,
[ --disable-protobuf Disable Protocol Buffers],
[use_protobuf=$enableval], [use_protobuf=yes])
if test "x$use_protobuf" = "xyes"; then
protobuf_error_msg="\nWARNING: You need to install Protocol Buffers to get faster program startup.\n Sources are available at http://code.google.com/p/protobuf/downloads/list\n Package names for Ubuntu/Debian: libprotobuf0, libprotobuf-dev, protobuf-compiler\n Package names for other distributions: protobuf, protobuf-devel\n Disabling protobuf.\n"
AC_CHECK_PROG(have_protoc, protoc, yes, no)
if test "x$have_protoc" = "xno"; then
echo -e $protobuf_error_msg; use_protobuf=no
else
AC_CHECK_LIB(protobuf, _ZN6google8protobuf7MessageD2Ev, [], [
echo -e $protobuf_error_msg; use_protobuf=no ], -lpthread)
if test "x$use_protobuf" = "xyes"; then
AC_LANG([C++])
AC_CHECK_HEADER([google/protobuf/message.h],,[
echo -e $protobuf_error_msg; use_protobuf=no ])
AC_LANG([C])
fi
fi
fi
AM_CONDITIONAL([USE_PROTOBUF], [test "x$use_protobuf" = "xyes"])
dnl Do we have the POSIX compatible scandir() prototype?
AC_CACHE_CHECK([whether we have the POSIX compatible scandir() prototype],
ac_cv_cxx_scandir_posix,[
AC_LANG_SAVE
AC_LANG_CPLUSPLUS
AC_TRY_COMPILE([
# include <dirent.h>
int func (const char *d, dirent ***list, void *sort) {
int n = scandir(d, list, 0, (int(*)(const dirent **, const dirent **))sort);
}
],[
], ac_cv_cxx_scandir_posix=yes, ac_cv_cxx_scandir_posix=no)
AC_LANG_RESTORE
])
if test "$ac_cv_cxx_scandir_posix" = yes; then
AC_DEFINE([HAVE_SCANDIR_POSIX], [], [POSIX Compatible scandir()])
fi
AC_CHECK_HEADERS([sys/inotify.h], [have_inotify=yes], [have_inotify=no])
AC_ARG_ENABLE(debug,
[ --enable-debug[=none,normal,full] Enable output of debug messages],
[enable_debug=$enableval], [enable_debug=none])
if test "x$enable_debug" = "xnone"; then
AC_DEFINE(DEBUGLEVEL, 0, [Debug level])
elif test "x$enable_debug" = "xfull"; then
AC_DEFINE(DEBUGLEVEL, 2, [Debug level])
else
AC_DEFINE(DEBUGLEVEL, 1, [Debug level])
fi
AC_CONFIG_FILES([
libcompizconfig.pc
Makefile
src/Makefile
backend/Makefile
plugin/Makefile
include/Makefile
metadata/Makefile
config/Makefile
])
AC_OUTPUT
if test "x$have_inotify" = xno; then
echo ""
echo "NOTE: "
echo "======"
echo ""
echo "Inotify header files not found. While this library might work" \
"without them, user experience is degraded as settings won't be" \
"applied instantly. We strongly suggest installing the inotify" \
"header files."
fi
## Process this file with automake to produce Makefile.in
ccsincludedir = $(includedir)/compizconfig
ccsinclude_HEADERS = ccs.h ccs-backend.h
/*
* Compiz configuration system library
*
* Copyright (C) 2007 Dennis Kasprzyk <onestone@opencompositing.org>
* Copyright (C) 2007 Danny Baumann <maniac@opencompositing.org>
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2.1 of the License, or (at your option) any later version.
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/
#ifndef CCS_BACKEND_H
#define CCS_BACKEND_H
#include <ccs.h>
typedef struct _CCSBackend CCSBackend;
typedef struct _CCSBackendVTable CCSBackendVTable;
struct _CCSBackend
{
void *dlhand;
CCSBackendVTable *vTable;
};
typedef CCSBackendVTable * (*BackendGetInfoProc) (void);
typedef void (*CCSExecuteEventsFunc) (unsigned int flags);
typedef Bool (*CCSInitBackendFunc) (CCSContext * context);
typedef Bool (*CCSFiniBackendFunc) (CCSContext * context);
typedef Bool (*CCSContextReadInitFunc) (CCSContext * context);
typedef void (*CCSContextReadSettingFunc)
(CCSContext * context, CCSSetting * setting);
typedef void (*CCSContextReadDoneFunc) (CCSContext * context);
typedef Bool (*CCSContextWriteInitFunc) (CCSContext * context);
typedef void (*CCSContextWriteSettingFunc)
(CCSContext * context, CCSSetting * setting);
typedef void (*CCSContextWriteDoneFunc) (CCSContext * context);
typedef Bool (*CCSGetIsIntegratedFunc) (CCSSetting * setting);
typedef Bool (*CCSGetIsReadOnlyFunc) (CCSSetting * setting);
typedef CCSStringList (*CCSGetExistingProfilesFunc) (CCSContext * context);
typedef Bool (*CCSDeleteProfileFunc) (CCSContext * context, char * name);
struct _CCSBackendVTable
{
char *name;
char *shortDesc;
char *longDesc;
Bool integrationSupport;
Bool profileSupport;
/* something like a event loop call for the backend,
so it can check for file changes (gconf changes in the gconf backend)
no need for reload settings signals anymore */
CCSExecuteEventsFunc executeEvents;
CCSInitBackendFunc backendInit;
CCSFiniBackendFunc backendFini;
CCSContextReadInitFunc readInit;
CCSContextReadSettingFunc readSetting;
CCSContextReadDoneFunc readDone;
CCSContextWriteInitFunc writeInit;
CCSContextWriteSettingFunc writeSetting;
CCSContextWriteDoneFunc writeDone;
CCSGetIsIntegratedFunc getSettingIsIntegrated;
CCSGetIsReadOnlyFunc getSettingIsReadOnly;
CCSGetExistingProfilesFunc getExistingProfiles;
CCSDeleteProfileFunc deleteProfile;
};
CCSBackendVTable* getBackendInfo (void);
#endif
This diff is collapsed.
prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
includedir=@includedir@
Name: libcompizconfig
Description: Compiz configuration system
Version: @VERSION@
Requires: compiz
Libs: -L@libdir@ -lcompizconfig
Cflags: -I@includedir@/compizconfig
metadir = $(datadir)/compiz
meta_DATA = ccp.xml
EXTRA_DIST = \
ccp.xml
<?xml version="1.0" encoding="UTF-8"?>
<compiz>
<plugin name="ccp">
<short>CCP</short>
<long>Compizconfig Settings Plugins</long>
</plugin>
</compiz>
AM_CPPFLAGS = \
@COMPIZ_CFLAGS@ \
-I$(top_srcdir)/include \
-I$(top_srcdir)/src \
-DPLUGINDIR=\"$(plugindir)\" \
-DLIBDIR=\"$(libdir)\"
libccp_la_LDFLAGS = -module -avoid-version -no-undefined
libccp_la_LIBADD = $(top_builddir)/src/libcompizconfig.la
libccp_la_SOURCES = ccp.c
moduledir = $(plugindir)
module_LTLIBRARIES = libccp.la
This diff is collapsed.
if USE_PROTOBUF
PROTOBUF_LIB = -lprotobuf
PROTOBUF_DEFINES = \
-DUSE_PROTOBUF=1
compizconfig.pb.cc: compizconfig.proto
protoc --cpp_out=. -I $(srcdir)/ $(srcdir)/compizconfig.proto
compizconfig.pb.h: compizconfig.pb.cc
nodist_libcompizconfig_la_SOURCES = \
compizconfig.pb.cc \
compizconfig.pb.h
BUILT_SOURCES = \
compizconfig.pb.cc \
compizconfig.pb.h
CLEANFILES = \
$(nodist_libcompizconfig_la_SOURCES)
endif
cc_srcdir = $(top_srcdir)/compizconfig/libcompizconfig
EXTRA_DIST = compizconfig.proto
AM_CPPFLAGS = \
@COMPIZ_CFLAGS@ \
@LIBX11_CFLAGS@ \
@LIBXML2_CFLAGS@ \
-I$(cc_srcdir)/include \
-I$(top_srcdir)/include \
-I$(top_builddir)/include \
-I$(cc_srcdir)/src \
-I$(top_srcdir) \
-DPLUGINDIR=\"$(PLUGINDIR)\" \
-DMETADATADIR=\"$(METADATADIR)\" \
-DLIBDIR=\"$(libdir)\" \
$(PROTOBUF_DEFINES) \
-DSYSCONFDIR=\"$(sysconfdir)\"
libcompizconfig_la_SOURCES = \
main.c \
lists.c \
compiz.cpp \
config.c \
iniparser.c \
ini.c \
bindings.c \
filewatch.c \
ccs-private.h \
iniparser.h
libcompizconfig_la_LIBADD = @LIBXML2_LIBS@ @LIBX11_LIBS@ $(PROTOBUF_LIB)
lib_LTLIBRARIES=libcompizconfig.la