50e2259404
This was a dubious "fix" for a Nvidia driver problem. The problem was never fully understood, and the then developers took a shotgun approach and implemented xsync fences as a fix. Which somehow fixed the problem. Again, I don't see any indication that the developers understood why this "fix" worked. (for details, see chjj/compton#152 and chjj/compton#181) The driver problem should have been fixed almost 5 years ago. So this shouldn't be needed anymore. In addition the way compton uses xsync fences is apparently wrong according to the xsync spec (fences are attached to screen, but compton uses them as if they were attached to drawables). So, I will try removing it and see if anyone will complain. If there are real concrete reasons why fences are needed, it will be brought back. Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
Compton
This is a development branch, bug to be expected
This is forked from the original Compton because that seems to have become unmaintained. I'll merge pull requests as they appear upstream, as well as trying to fix bugs reported to upstream, or found by myself.
The original README can be found here
Build
Dependencies
Assuming you already have all the usual building tools installed (e.g. gcc, meson, ninja, etc.), you still need:
- libx11
- libXext
- xproto
- xcb
- xcb-damage
- xcb-xfixes
- xcb-shape
- xcb-renderutil
- xcb-render
- xcb-randr
- xcb-composite
- xcb-image
- xcb-xinerama (optional, disable with
-Dxinerama=falsemeson configure flag) - pixman
- libdbus (optional, disable with the
-Ddbus=falsemeson configure flag) - libconfig (optional, disable with the
-Dconfig_file=falsemeson configure flag) - libGL (optional, disable with the
-Dopengl=falsemeson configure flag) - libpcre (optional, disable with the
-Dregex=falsemeson configure flag) - libev
To build the documents, you need asciidoc
How to build
$ meson --buildtype=release . build
$ ninja -C build
Built binary can be found in build/src
How to Contribute
Code
You can look at the Projects page, and see if there is anything interests you. Or you can take a look at the Issues.
Non-code
Even if you don't want to contribute code, you can still contribute by compiling and running this branch, and report any issue you can find.
Contributors
See CONTRIBUTORS