mirror of
https://github.com/Llewellynvdm/conky.git
synced 2024-12-27 20:44:56 +00:00
Check out my config at gist :)
https://gist.github.com/Llewellynvdm/02279631eabc65601a5722dcf4780768
f695ed58d9
This makes sure valgrind doesn't show false memleaks that are caused by ncurses instead of our code when we do a 'Debug' build. There is a also a disadvantage: When your ncurses library is not build with the '--disable-leaks' option (this is the case in the default version of ncurses of most distro's) and you build conky with ncurses and debug turned on then you will see a segmentation fault when you stop conky. On the other hand people that want to build conky as a debug build with ncurses support will probably also have a ncurses with --disable-leaks ... |
||
|---|---|---|
| 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).