mirror of
https://github.com/Llewellynvdm/conky.git
synced 2025-01-27 09:08:25 +00:00
98196d0e6b
* don't use kvm_* calls, just sysctl (so no suid perm necessary) * sysctls calls in general aren't thread safe, collapse callbacks using same sysctls (specifically total/running procs and proc list ones). Some sysctls need two calls (first to get size of obj returned, second to get object self); if different threads use this schema on same sysctl, weird values are returned (first/second calls sequence should be serialized). In general it makes not much sense too having more threads that use the same sysctl; just get info once and populate all data. * add DragonFly specific extended uname string ($version in conky.conf) with git version and signature Todo: - top process list logic is old style, use top.cc funcs. - find a solution for cpu freq Signed-off-by: Pavel Labath <pavelo@centrum.sk>
Hello, there. Using CMake to build Conky is pretty easy, and here is how I do it: 1. From the top level source dir, create a build working dir, and cd into it $ mkdir build $ cd build 2. Run the cmake configuration process $ cmake ../ # pass the path to the sources to cmake OR $ ccmake ../ # you can also use the fance curses interface, or try cmake-gui 3. Compile as usual, and enjoy the out-of-source goodness $ make # make install # if you want There are a number of build options for Conky, and the best way to discover them is to use the ccmake (or cmake-gui) CMake tool for browsing them. Certain Conky build time features (such as doc generation) require third-party applications, which you should be notified of via CMake. In the case of doc generation, you'll need the docbook2X package (available on most distributions).