mirror of
https://github.com/Llewellynvdm/conky.git
synced 2024-12-25 20:11:11 +00:00
Check out my config at gist :)
https://gist.github.com/Llewellynvdm/02279631eabc65601a5722dcf4780768
5a7ec7fb0b
As i said in my rant somewhere, it's up to the person catching the exception to decide if the error is critical or not. The person throwing the exception should specify the type of error and that's where his job ends. |
||
---|---|---|
cmake | ||
data | ||
doc | ||
extras | ||
lua | ||
src | ||
.gitignore | ||
AUTHORS | ||
autogen.sh | ||
changelog2html.py | ||
ChangeLog | ||
check_docs.py | ||
CMakeLists.txt | ||
COPYING | ||
INSTALL | ||
LICENSE.BSD | ||
LICENSE.GPL | ||
NEWS | ||
README.cmake | ||
text2c.sh | ||
TODO |
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).