You are not logged in.
I've been using compiz-git from the AUR, but recently Sam Spilsbury has said that he will henceforth only use launchpad for Compiz development and that the launchpad branch is already more updated than the git branch.
But I know nothing about bzr.
If I do
bzr checkout lp:compizI get a bunch of files, but I don't know how to build it after that! There are no makefiles...
Offline
Did you check /usr/share/pacman/PKGBUILD-bzr.proto as an exemple?
Offline
No I didn't... because I don't have one of those.
Where do I find this bzr-proto file?
Offline
It's included in extra/abs.
Offline
I can give you a *rough* very manual howto for compiz from bzr, but i don't half time to really maintain pkgbuilds for compiz-bzr, but i have built compiz 0.9.7 recently.
You basically have a few bzr branches your going to have to check out;
Compiz-core (this is the master branch in bzr)
bzr branch lp:compiz-coreCompiz-plugins-main
bzr branch lp:compiz-plugins-mainCompiz-plugins-extra
bzr branch lp:compiz-plugins-extraCompiz-libcompizconfig
bzr branch lp:compiz-libcompizconfigCompiz-libcompizconfig-python
bzr branch lp:compiz-compizconfig-pythonCompiz-ccsm
bzr branch lp:compiz-ccsm...and i think that is it.
You build each component (roughly in the above order). simply cd into the directory and;
mkdir build
cd build
cmake .. (installs to /usr/local) or cmake .. -DCMAKE_INSTALL_PREFIX=/usr (or whatever prefix you like)
make
sudo make installNOTE: 2 exceptions to this are Compiz-ccsm && Compiz-libcompizconfig-python ~ this is because they both use python in the build process, and therefore need to be told to use python2 rather than python (which is obviously python3 in Arch).
in both cases, you just just edit the CMakeLists.txt included *before* running 'cmake ..' from within the build directory
The original will look something like this;
add_custom_target (python ALL
COMMAND python setup.py build
WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}
COMMENT "Generating Python Bytecode")But for Archlinux, it should read;
add_custom_target (python ALL
COMMAND python2 setup.py build
WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}
COMMENT "Generating Python Bytecode")Note: You could use the sed command in your package build
I hope this helps ![]()
Oh, and i would actually go to lp:compiz-core and take a look around, i know Sam had been changing some stuff around. ie: not too long ago, the majority of plugins each had their own bzr branch, but now that GIT isn't being used they were merged into 'main' and 'extra' plugins. However, the last time i built compiz (like a week ago, 0.9.7 - this method worked fine).
cheerz
Last edited by triplesquarednine (2012-02-06 19:25:10)
Offline