Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>pull/1/head
parent
14e1aa2006
commit
884c8093d6
GPG Key ID:
2A75B7CA8ADED5CF
@ -0,0 +1 @@
|
||||
Dennis Kasprzyk <onestone@beryl-project.org>
|
||||
@ -0,0 +1,236 @@
|
||||
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.
|
||||
|
||||
@ -0,0 +1,7 @@
|
||||
## Process this file with automake to produce Makefile.in
|
||||
SUBDIRS = src
|
||||
|
||||
EXTRA_DIST = VERSION
|
||||
|
||||
pkgconfigdir = $(datadir)/pkgconfig
|
||||
pkgconfig_DATA = bcop.pc
|
||||
@ -0,0 +1 @@
|
||||
There is nothing here yet.
|
||||
@ -0,0 +1 @@
|
||||
VERSION=0.8.4
|
||||
@ -0,0 +1,13 @@
|
||||
#! /bin/sh
|
||||
|
||||
srcdir=`dirname $0`
|
||||
test -z "$srcdir" && srcdir=.
|
||||
|
||||
ORIGDIR=`pwd`
|
||||
cd $srcdir
|
||||
|
||||
autoreconf -v --install || exit 1
|
||||
cd $ORIGDIR || exit $?
|
||||
|
||||
$srcdir/configure "$@"
|
||||
|
||||
@ -0,0 +1,13 @@
|
||||
prefix=@prefix@
|
||||
exec_prefix=@exec_prefix@
|
||||
datarootdir=@datarootdir@
|
||||
datadir=@datadir@
|
||||
includedir=@includedir@
|
||||
bin=@exec_prefix@/bin/bcop
|
||||
xsltpath=@prefix@/share/bcop
|
||||
|
||||
Name: bcop
|
||||
Description: Compiz option code generator
|
||||
Version: @VERSION@
|
||||
Requires:
|
||||
|
||||
@ -0,0 +1,27 @@
|
||||
AC_PREREQ(2.57)
|
||||
|
||||
AC_INIT([compiz-bcop],esyscmd(. ./VERSION;echo -n $VERSION), [onestone@beryl-project.org])
|
||||
|
||||
AC_DEFINE_UNQUOTED(VERSION,"$VERSION",[Version])
|
||||
|
||||
AM_INIT_AUTOMAKE([1.9 dist-bzip2])
|
||||
AC_CONFIG_HEADER([config.h])
|
||||
AM_MAINTAINER_MODE
|
||||
|
||||
AC_ISC_POSIX
|
||||
AC_PROG_CC
|
||||
AC_HEADER_STDC
|
||||
|
||||
AC_C_BIGENDIAN
|
||||
|
||||
PKG_CHECK_MODULES(LIBXSLT, libxslt)
|
||||
|
||||
xsltdir=$datadir/bcop
|
||||
AC_SUBST(xsltdir)
|
||||
|
||||
AC_OUTPUT([
|
||||
bcop.pc
|
||||
Makefile
|
||||
src/Makefile
|
||||
src/bcop
|
||||
])
|
||||
@ -0,0 +1,60 @@
|
||||
compiz-fusion-bcop-trinity (0.8.4-3debian11.0.0+4~a) bullseye; urgency=low
|
||||
|
||||
* Change debhelper compatibility level to 9
|
||||
|
||||
-- Slรกvek Banko <slavek.banko@axis.cz> Wed, 08 Apr 2020 01:25:35 +0200
|
||||
|
||||
compiz-fusion-bcop-trinity (0.8.4-3ubuntu20.04.0+3~a) focal; urgency=low
|
||||
|
||||
* Change debhelper compatibility level to 7
|
||||
|
||||
-- Slรกvek Banko <slavek.banko@axis.cz> Sat, 13 Aug 2016 18:53:28 +0200
|
||||
|
||||
compiz-fusion-bcop-trinity (0.8.4-3ubuntu16.10.0+2~a) yakkety; urgency=low
|
||||
|
||||
* Trinity changes pulled into a separate patch
|
||||
|
||||
-- Slรกvek Banko <slavek.banko@axis.cz> Thu, 14 Mar 2013 18:44:40 +0100
|
||||
|
||||
compiz-fusion-bcop-trinity (0.8.4-1debian7) squeeze; urgency=low
|
||||
|
||||
* Hardcoded pkg-config directory to location of bcop.pc
|
||||
* Moved KDE3 to /opt/trinity
|
||||
* Integrated properly with KDE4.2+
|
||||
* Added -trinity suffix
|
||||
|
||||
-- Timothy Pearson <kb9vqf@pearsoncomputing.net> Fri, 06 March 2009 01:35:00 -0600
|
||||
|
||||
compiz-fusion-bcop (0.8.4-1) unstable; urgency=low
|
||||
|
||||
* New upstream release
|
||||
|
||||
-- Sean Finney <seanius@debian.org> Thu, 04 Feb 2010 18:04:13 +0100
|
||||
|
||||
compiz-fusion-bcop (0.8.2-1) unstable; urgency=low
|
||||
|
||||
* New upstream release
|
||||
* add gbp.conf for use with git-buildpackage
|
||||
* lintian fixes:
|
||||
- update Standards-Version to 3.8.1
|
||||
- build binary in binary-indep, not binary-arch
|
||||
|
||||
-- Sean Finney <seanius@debian.org> Sun, 05 Apr 2009 22:16:11 +0200
|
||||
|
||||
compiz-fusion-bcop (0.7.6-1) unstable; urgency=low
|
||||
|
||||
* New upstream release.
|
||||
|
||||
-- Sean Finney <seanius@debian.org> Tue, 03 Jun 2008 00:45:02 +0200
|
||||
|
||||
compiz-fusion-bcop (0.7.4-1) unstable; urgency=low
|
||||
|
||||
* New upstream release.
|
||||
|
||||
-- Sean Finney <seanius@debian.org> Mon, 19 May 2008 19:48:56 +0200
|
||||
|
||||
compiz-fusion-bcop (0.6.0-1) unstable; urgency=low
|
||||
|
||||
* Initial release (Closes: #431756).
|
||||
|
||||
-- Sean Finney <seanius@debian.org> Fri, 09 Nov 2007 19:04:28 +0100
|
||||
@ -0,0 +1 @@
|
||||
9
|
||||
@ -0,0 +1,18 @@
|
||||
Source: compiz-fusion-bcop-trinity
|
||||
Section: deps-r14/x11
|
||||
Priority: extra
|
||||
Maintainer: Timothy Pearson <kb9vqf@pearsoncomputing.net>
|
||||
Build-Depends: cdbs, debhelper (>= 9~), quilt, intltool, libtool, libglib2.0-dev, libxslt1-dev, pkg-config
|
||||
Standards-Version: 3.8.1
|
||||
|
||||
Package: compiz-fusion-bcop-trinity
|
||||
Architecture: all
|
||||
Depends: pkg-config, xsltproc
|
||||
Description: Compiz Fusion option code generator [Trinity]
|
||||
Compiz Fusion is the result of the re-unification of the Beryl-project
|
||||
and the community around the Compiz Window Manager. It seeks to provide
|
||||
an easy and fun-to-use windowing environment, allowing use of the
|
||||
graphics hardware to provide impressive effects, amazing speed and
|
||||
unrivalled usefulness
|
||||
.
|
||||
This tool is used to generate code for use with compiz-fusion plugins.
|
||||
@ -0,0 +1,34 @@
|
||||
This package was debianized by sean finney <seanius@debian.org> on
|
||||
Mon, 15 Oct 2007 19:49:50 +0200.
|
||||
|
||||
It was downloaded from: git://anongit.compiz-fusion.org/fusion/libraries/bcop
|
||||
|
||||
Upstream Author:
|
||||
|
||||
Dennis Kasprzyk <onestone@beryl-project.org>
|
||||
|
||||
Copyright:
|
||||
|
||||
Copyright (C) 2007 Dennis Kasprzyk
|
||||
|
||||
License:
|
||||
|
||||
This package is free software; you can redistribute it and/or modify
|
||||
it under the terms of the GNU General Public License as published by
|
||||
the Free Software Foundation; either version 2 of the License, or
|
||||
(at your option) any later version.
|
||||
|
||||
This package 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 General Public License for more details.
|
||||
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with this package; if not, write to the Free Software
|
||||
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
|
||||
|
||||
On Debian systems, the complete text of the GNU General
|
||||
Public License can be found in `/usr/share/common-licenses/GPL'.
|
||||
|
||||
The Debian packaging is (C) 2007, sean finney <seanius@debian.org> and
|
||||
is licensed under the GPL, see `/usr/share/common-licenses/GPL'.
|
||||
@ -0,0 +1 @@
|
||||
opt/trinity/bin
|
||||
@ -0,0 +1,2 @@
|
||||
NEWS
|
||||
README
|
||||
@ -0,0 +1,13 @@
|
||||
Index: b/src/bcop.in
|
||||
===================================================================
|
||||
--- a/src/bcop.in 2013-03-14 18:48:32.000000000 +0100
|
||||
+++ b/src/bcop.in 2013-03-14 18:48:46.000000000 +0100
|
||||
@@ -18,7 +18,7 @@
|
||||
# GNU General Public License for more details.
|
||||
#
|
||||
|
||||
-xsltdir=@prefix@/share/bcop
|
||||
+xsltdir=`PKG_CONFIG_PATH=/opt/trinity/share/pkgconfig pkg-config --variable xsltpath bcop`
|
||||
|
||||
function usage
|
||||
{
|
||||
@ -0,0 +1 @@
|
||||
099-trinity.diff
|
||||
@ -0,0 +1,19 @@
|
||||
#!/usr/bin/make -f
|
||||
|
||||
include /usr/share/cdbs/1/class/autotools.mk
|
||||
include /usr/share/cdbs/1/rules/debhelper.mk
|
||||
|
||||
DEB_CONFIGURE_INCLUDEDIR := /opt/trinity/include
|
||||
DEB_CONFIGURE_MANDIR := /opt/trinity/share/man
|
||||
DEB_CONFIGURE_PREFIX := /opt/trinity
|
||||
DEB_CONFIGURE_INFODIR := /opt/trinity/share/info
|
||||
|
||||
cdbs_configure_flags := --with-qt-dir=/usr/share/qt3 --disable-rpath --with-xinerama $(cdbs_kde_enable_final) $(cdbs_kde_enable_debug)
|
||||
|
||||
DEB_CONFIGURE_EXTRA_FLAGS := --prefix=/opt/trinity --with-extra-libs=/opt/trinity/lib --with-extra-includes=/opt/trinity/include
|
||||
|
||||
makebuilddir:: debian/stamp-autoreconf
|
||||
debian/stamp-autoreconf:
|
||||
dh_testdir
|
||||
autoreconf -vi
|
||||
touch debian/stamp-autoreconf
|
||||
@ -0,0 +1 @@
|
||||
3.0 (quilt)
|
||||
@ -0,0 +1,6 @@
|
||||
# Use xz instead of gzip
|
||||
compression = "xz"
|
||||
compression-level = 9
|
||||
|
||||
# Don't run differences
|
||||
diff-ignore = .*
|
||||
@ -0,0 +1,10 @@
|
||||
xmldir = $(xsltdir)
|
||||
xml_files = bcop.xslt
|
||||
xml_DATA = $(xml_files)
|
||||
|
||||
bin_SCRIPTS = bcop
|
||||
|
||||
DISTCLEANFILES=$(bin_SCRIPTS)
|
||||
|
||||
EXTRA_DIST=bcop.in \
|
||||
$(xml_files)
|
||||
@ -0,0 +1,75 @@
|
||||
#!/bin/bash
|
||||
#
|
||||
#
|
||||
# Compiz option code generator
|
||||
#
|
||||
# Copyright : (C) 2007 by Dennis Kasprzyk
|
||||
# E-mail : onestone@beryl-project.org
|
||||
#
|
||||
#
|
||||
# This program is free software; you can redistribute it and/or
|
||||
# modify it under the terms of the GNU General Public License
|
||||
# as published by the Free Software Foundation; either version 2
|
||||
# of the License, or (at your option) any later version.
|
||||
#
|
||||
# This program 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 General Public License for more details.
|
||||
#
|
||||
|
||||
xsltdir=@prefix@/share/bcop
|
||||
|
||||
function usage
|
||||
{
|
||||
echo "Usage: $0 [options] <options file>"
|
||||
echo "Options:"
|
||||
echo " -h, --help display this help message"
|
||||
echo " -v, --version print version information"
|
||||
echo " --source=<file> source file name"
|
||||
echo " --header=<file> header file name"
|
||||
exit 1
|
||||
}
|
||||
|
||||
srcfile=
|
||||
hdrfile=
|
||||
|
||||
set -- `getopt -quo "hv" -l "help,version,source:,header:" -- "$@"`
|
||||
[ $# -lt 2 ] && usage
|
||||
|
||||
while [ $# -gt 0 ]
|
||||
do
|
||||
case "$1" in
|
||||
-h) usage;;
|
||||
--help) usage;;
|
||||
-v) echo "@PACKAGE_STRING@"; exit 0;;
|
||||
--version) echo "@PACKAGE_STRING@"; exit 0;;
|
||||
--source) srcfile="$2"; shift;;
|
||||
--header) hdrfile="$2"; shift;;
|
||||
--) shift; break;;
|
||||
-*) usage;;
|
||||
*) break;; # terminate while loop
|
||||
esac
|
||||
shift
|
||||
done
|
||||
|
||||
xmlfile="$1"
|
||||
|
||||
if [ -e $xmlfile ]; then
|
||||
if [ -n "$hdrfile" ]; then
|
||||
xsltproc --stringparam "header" "true" $xsltdir/bcop.xslt $xmlfile > "$hdrfile"
|
||||
RETVAL=$?
|
||||
if [ $RETVAL -ne 0 ]; then
|
||||
rm -f $hdrfile
|
||||
exit $RETVAL
|
||||
fi
|
||||
fi
|
||||
if [ -n "$srcfile" ]; then
|
||||
xsltproc --stringparam "source" "true" $xsltdir/bcop.xslt $xmlfile > "$srcfile"
|
||||
RETVAL=$?
|
||||
if [ $RETVAL -ne 0 ]; then
|
||||
rm -f $srcfile
|
||||
exit $RETVAL
|
||||
fi
|
||||
fi
|
||||
fi
|
||||
File diff suppressed because it is too large
Load Diff
Binary file not shown.
@ -0,0 +1,50 @@
|
||||
Lead Developers:
|
||||
--------------------------------------------
|
||||
Danny Baumann <dannybaumann@web.de>
|
||||
David Reveman <davidr@novell.com>
|
||||
Dennis Kasprzyk <onestone@opencompositing.org>
|
||||
Erkin Bahceci <erkinbah@gmail.com>
|
||||
iXce - Guillaume Seguin <guillaume@segu.in>
|
||||
Kristian Lyngstรธl <kristian@bohemians.org>
|
||||
|
||||
Contributors:
|
||||
--------------------------------------------
|
||||
Andrew Wedderburn(artwork) <andrew.wedderburn@gmail.com>
|
||||
Treviรฑo - 3v1n0 <trevi55@gmail.com>
|
||||
Travis Watkins <amaranth@ubuntu.com>
|
||||
Roland Baer
|
||||
Robert Carr
|
||||
Quinnstorm <livinglatexkali@gmail.com>
|
||||
Roi Cohen <roico.beryl@gmail.com>
|
||||
Diogo Ferreira <diogo.ferreira@gmail.com>
|
||||
|
||||
Translators:
|
||||
--------------------------------------------
|
||||
de Patrick Niklaus <patrick.niklaus@googlemail.com>, Danny Baumann <dannybaumann@web.de>, Nick Bauermeister <Forlong@gmx.de>, Thorsten Sperber <trex2003@gmx.de>, Markus Latarius <markus.latarius@gmail.com>, Johannes Engel <j-engel@gmx.de>
|
||||
el ฮฮทฮผฮฎฯฯฮทฯ (djdoo) <jimdusis@yahoo.gr>, ฮฮฑฯฮฏฮปฮทฯ (Aneurysm) <bill_rapman@yahoo.com>, ฮฯฯฯฮฑฯ (diafanos) <kostasagn@hotmail.com>, Thodo Mitch (Teddy) <thodo_mitch@hotmail.com>, Dimman Ramone (dimmanramone) <ramone@online.ie>
|
||||
fr iXce - Guillaume Seguin <guillaume@segu.in>, Sylvain Debray (syldeb35) <sylvain.debray@wanadoo.fr>, xsnake - Carl Garand <carlgarand@hotmail.com>
|
||||
gu Ankit Patel <ankit@redhat.com>
|
||||
it Marco Trevisan (Treviรฑo) <trevi55@gmail.com>, Fabio Fiorentini (Ahren / FaBBio) <fabio.fiorentini@gmail.com>, Andrea De Iacovo (Firstbit)<andrea.de.iacovo@gmail.com>, Emiliano Perulli <emiliano.perulli@alice.it>
|
||||
pl Karol Sikora (elektrrrus) <elektrrrus at gmail dot com>, Adam Kremienowski (kremien) <akremien at gmail dot com>, Jakub Chromiak (silverado)<silvervoxer@gmail.com>, Mariusz Fik (fisiu) <fisiu82@gmail.com>
|
||||
pt Nicolau Goncalves (Excentrik) <excentriko@gmail.com>
|
||||
sv Daniel Nylander <po@danielnylander.se>, Erik Eloff (Loffe) <erik@eloff.se>
|
||||
zh Thruth Wang <gubotruth@gmail.com>
|
||||
|
||||
Note:
|
||||
-------------------------------------------------------------------------------
|
||||
If you have contributed something significant to fusion-plugins
|
||||
and your name is missing here, please email the lead developers
|
||||
with your Full name, email address, country and a brief
|
||||
reminder of what you have done.
|
||||
|
||||
Format :
|
||||
-------------------------------------------------------------------------------
|
||||
In order to parse AUTHORS files some rules must be followed :
|
||||
|
||||
1 - Each first chapter line must end by ':'
|
||||
The recognized chapter names are :
|
||||
"Developer:", "Developers:", "Contributors:", Note:", "Website:", "Documenters:"
|
||||
and "Translators:".
|
||||
|
||||
2 - Each item of the "Translators" chapter must begin by the locale keyword.
|
||||
This keyword must be followed by a space.
|
||||
@ -0,0 +1,27 @@
|
||||
project (compiz-plugins-extra)
|
||||
|
||||
cmake_minimum_required (VERSION 2.4)
|
||||
|
||||
set (CMAKE_MODULE_PATH ${CMAKE_CURRENT_SOURCE_DIR}/cmake)
|
||||
include (cmake/addons.cmake)
|
||||
include (cmake/CompizFusion.cmake)
|
||||
|
||||
get_version ()
|
||||
|
||||
set (CF_INSTALL_TYPE package)
|
||||
|
||||
set (CF_MIN_COMPIZ_VERSION ${VERSION})
|
||||
set (CF_MIN_BCOP_VERSION ${VERSION})
|
||||
|
||||
set (CF_PLUGIN_INCLUDE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/include")
|
||||
set (CF_PLUGIN_PKGCONFIG_DIR "${CMAKE_CURRENT_SOURCE_DIR}")
|
||||
set (CF_PLUGIN_XML_DIR "${CMAKE_CURRENT_SOURCE_DIR}/metadata")
|
||||
set (CF_PLUGIN_I18N_DIR "${CMAKE_CURRENT_SOURCE_DIR}/po")
|
||||
|
||||
compiz_fusion_add_uninstall ()
|
||||
cf_add_plugins (src)
|
||||
cf_install_plugin_data_files (images)
|
||||
cf_install_plugin_data_files (data)
|
||||
cf_print_plugin_configure_results (src)
|
||||
|
||||
cf_add_package_generation ("Compiz Plugins Extra")
|
||||
@ -0,0 +1,236 @@
|
||||
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.
|
||||
|
||||