mirror of
https://github.com/Llewellynvdm/conky.git
synced 2024-11-15 09:44:04 +00:00
Check out my config at gist :)
https://gist.github.com/Llewellynvdm/02279631eabc65601a5722dcf4780768
ccc50cef48
when the system clock is moved backwards, the update interval would be calculated incorrectly. If it was moved back far enough, conky would use 100% cpu. Conky now uses monotonic clock to prevent this. If it turns out to be unsupported on some platform, an appropriate fallback can be added. problem reported by norsetto |
||
---|---|---|
data | ||
doc | ||
extras | ||
lua | ||
m4 | ||
src | ||
.gitignore | ||
AUTHORS | ||
autogen.sh | ||
changelog2html.py | ||
ChangeLog | ||
check_docs.py | ||
config.rpath | ||
configure.ac.in | ||
COPYING | ||
INSTALL | ||
LICENSE.BSD | ||
LICENSE.GPL | ||
Makefile.am | ||
NEWS | ||
README.git-version | ||
text2c.sh | ||
TODO |
QUICK & EASY: $ sh autogen.sh $ ./configure $ make $ ./src/conky # to run Conky # make install First, read the README. This contains instructions specific to building conky fresh from the git repo: * Conky requires three "auto-tools", with at least the specific version numbers. Make sure these are installed: aclocal-1.9 automake-1.9 autoconf-2.59 * NOTE: You may also need to install docbook2X for generating the documentation. Conky will check for the following programs in PATH during configuration: db2x_xsltproc db2x_manxml xsltproc * In the directory where you cloned conky from git, run "aclocal", "automake", and then "autoconf". Make sure you run those commands with the latest versions... it is very possible that older versions are installed, and plain "automake" really means automake-1.4, not what we want, but "automake-1.9" instead. Use the "--version" option to check the program version, i.e. "autoconf --version". You can also try using the autogen.sh script, like so: $ sh autogen.sh * After that, it's the familiar $ ./configure $ make # make install You might have to do the last step as root.