mirror of
https://github.com/Llewellynvdm/conky.git
synced 2024-12-26 12:27:52 +00:00
Check out my config at gist :)
https://gist.github.com/Llewellynvdm/02279631eabc65601a5722dcf4780768
93c6baebb6
This will allow us to get 304 responses back from remote URLs that we are grabbing using the curl, weather, and rss plugins. The first time we fetch a resource, we will always get the full content, but from there on out we will store any provided 'Etag' or 'Last-Modified' header, and submit these on the next request. If we get a 304 response back, we won't have to do any work at all. This benefits both us (bandwidth and parsing savings) and remote URLs (we actually make an attempt to not retrieve the same resource over and over again). |
||
|---|---|---|
| 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).