View Full Version : Compiz non-core plugins install script
mikedee
May 20th, 2007, 06:39 PM
Here is a very quick script which pulls and installs all the plugins I am aware of.
http://www.anykeysoftware.co.uk/compiz/compiz-plugin-install
Its a bit rough at the moment and does not cope well with errors (it just ignores them).
To install it type this
wget http://www.anykeysoftware.co.uk/compiz/compiz-plugin-install
chmod +x compiz-plugin-install
sudo mv compiz-plugin-install /usr/local/bin
It installs these plugins
addhelper, bs, bench, expo, fakeargb, group, mblur, opacify, quickchange, ring, snow, trailfocus, winrules
animation, cheatsheet, compiz-scheme, extrawm, firepaint, jpeg, mousegestures, put, reflex, screensaver, thumbnail, wall
crashhandler, fadedesktop, flash, kiosk, neg, python, resizeinfo, showdesktop, tile, widget
If you want to install beryl plugins then you will need to install bcop like this.
git clone git://anongit.opencompositing.org/compcomm/libraries/bcop
cd bcop
./autogen.sh --prefix=/usr/local
make
sudo make install
It seems to work fine from what I have tested, if none of the bcop'd plugins compile then try copying bcop.pc from the bcop directory to /usr/lib/pkgconfig it was not copied properly by the bcop install for me.
maniac
May 21st, 2007, 07:40 AM
If you want to install beryl plugins then you will need to install bcop like this.
Beryl plugins? Which Beryl plugins? ;)
git clone git://anongit.opencompositing.org/compcomm/libraries/bcop
cd bcop
./autogen.sh --prefix=/usr/local
make
sudo make install
It seems to work fine from what I have tested, if none of the bcop'd plugins compile then try copying bcop.pc from the bcop directory to /usr/lib/pkgconfig it was not copied properly by the bcop install for me.
This is not entirely correct. bcop.pc is (properly) installed to $PREFIX/lib/pkgconfig. The problem is that usually only /usr/lib/pkgconfig is in the pkg-config search path, so a
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
should do the trick. Obviously you need to adjust the path to your chosen prefix ;)
Maybe this line would suit best in your .bashrc file.
mikedee
May 21st, 2007, 11:36 AM
If you want to install beryl plugins then you will need to install bcop like this.
Beryl plugins? Which Beryl plugins? ;)
Im not sure, most of them I think. If you are not sure, you can type this to find out
grep Bcop */*.xml
This is not entirely correct. bcop.pc is (properly) installed to $PREFIX/lib/pkgconfig. The problem is that usually only /usr/lib/pkgconfig is in the pkg-config search path, so a
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
should do the trick. Obviously you need to adjust the path to your chosen prefix ;)
Maybe this line would suit best in your .bashrc file.
This is right, it was installed there. Maybe its because I am using a fairly fresh install and /usr/local/lib was not added to the PKGCONFIG path.
I notice a lot of users are having this same problem. Maybe it would be easier for everyone if you bcop'd files before checking them into git, that way only developers need to install bcop.
maniac
May 21st, 2007, 02:01 PM
If you want to install beryl plugins then you will need to install bcop like this.
Beryl plugins? Which Beryl plugins? ;)
Hmm, looks like my joke failed - I meant there are no Beryl plugins in existance anymore ;)
This is not entirely correct. bcop.pc is (properly) installed to $PREFIX/lib/pkgconfig. The problem is that usually only /usr/lib/pkgconfig is in the pkg-config search path, so a
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
should do the trick. Obviously you need to adjust the path to your chosen prefix ;)
Maybe this line would suit best in your .bashrc file.
This is right, it was installed there. Maybe its because I am using a fairly fresh install and /usr/local/lib was not added to the PKGCONFIG path.
I notice a lot of users are having this same problem. Maybe it would be easier for everyone if you bcop'd files before checking them into git, that way only developers need to install bcop.
No, I don't think that's the way to go. Autogenerated files should never be in the repo. Besides that, it should be no problem for people who build from git to install BCOP ;)
But having the BCOP generated source files in the release tarballs might be a good idea.
mikedee
June 6th, 2007, 04:46 PM
I have just updated this to include these new plugins:
notification
scaleaddon
text (required by scaleaddon)
wallpaper
boneyjellyfish
June 11th, 2007, 07:48 PM
Hi, I'm having several problems running your script (using Ubuntu 7.04 Feisty).
First, I just want to point out that running this script under feisty requires changing the commands in the script from git pull to git-pull, and to git-clean, as well as installing the package cogito.
Anyway, after making these changes and running the script, only a couple of the plugins actually installed. These plugins were:
libbs.so
libflash.so
libkiosk.so
libmousegestures.so
libquickchange.so
And all were installed to ~/.compiz/plugins
I went into the directory widget and tried to manually create it. Running either make or make install produce this lengthy error message:
libtool --mode=compile gcc -Wall -g `pkg-config --cflags compiz` -shared -c -o widget.lo widget.c
gcc -Wall -g -I/usr/include/libpng12 -I/usr/include/startup-notification-1.0 -I/usr/include/compiz -shared -c widget.c -fPIC -DPIC -o .libs/widget.o
widget.c:57: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'widgetMetadata'
widget.c:820: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'widgetDisplayOptionInfo'
widget.c: In function 'widgetInitDisplay':
widget.c:835: warning: implicit declaration of function 'compInitDisplayOptionsFromMetadata'
widget.c:836: error: 'widgetMetadata' undeclared (first use in this function)
widget.c:836: error: (Each undeclared identifier is reported only once
widget.c:836: error: for each function it appears in.)
widget.c:837: error: 'widgetDisplayOptionInfo' undeclared (first use in this function)
widget.c:848: warning: implicit declaration of function 'compFiniDisplayOptions'
widget.c: At top level:
widget.c:877: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'widgetScreenOptionInfo'
widget.c: In function 'widgetInitScreen':
widget.c:896: warning: implicit declaration of function 'compInitScreenOptionsFromMetadata'
widget.c:897: error: 'widgetMetadata' undeclared (first use in this function)
widget.c:898: error: 'widgetScreenOptionInfo' undeclared (first use in this function)
widget.c: In function 'widgetFiniScreen':
widget.c:946: warning: implicit declaration of function 'compFiniScreenOptions'
widget.c: In function 'widgetInit':
widget.c:984: warning: implicit declaration of function 'compInitPluginMetadataFromInfo'
widget.c:984: error: 'widgetMetadata' undeclared (first use in this function)
widget.c:986: error: 'widgetDisplayOptionInfo' undeclared (first use in this function)
widget.c:988: error: 'widgetScreenOptionInfo' undeclared (first use in this function)
widget.c:995: warning: implicit declaration of function 'compFiniMetadata'
widget.c:999: warning: implicit declaration of function 'compAddMetadataFromFile'
widget.c: In function 'widgetFini':
widget.c:1009: error: 'widgetMetadata' undeclared (first use in this function)
widget.c: At top level:
widget.c:1019: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
widget.c:1027: warning: initialization from incompatible pointer type
widget.c:1028: error: 'widgetGetMetadata' undeclared here (not in a function)
widget.c:1029: warning: initialization from incompatible pointer type
widget.c:1030: warning: initialization from incompatible pointer type
widget.c:1031: warning: initialization from incompatible pointer type
widget.c:1032: warning: initialization from incompatible pointer type
widget.c:1033: warning: initialization from incompatible pointer type
widget.c:1034: warning: initialization from incompatible pointer type
widget.c:1035: warning: initialization from incompatible pointer type
widget.c:1036: warning: initialization from incompatible pointer type
widget.c:1037: warning: initialization from incompatible pointer type
widget.c:1038: warning: initialization from incompatible pointer type
widget.c:1039: warning: initialization from incompatible pointer type
widget.c:1040: warning: initialization from incompatible pointer type
make: *** [widget.lo] Error 1
I receive very similar errors when trying to compile any of the other plugins that failed to install.
Any ideas? I'd really love to get these plugins to work--especially widget, for screenlets, and showdesktop. Neither of them are included in the moshen.de repository for some reason.
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.