(confuses vim)

Of course, messing up with os.environ breaks
other tests ...

This is a bug we still have to fix.
Patches welcome!

* Do not use a config.py.in configured by cmake to find cmake
  That's too overkill and not very reliable anyway

* Now honor CMAKE_INSTALL_PREFIX

* Get rid of magic qibuild.CMAKE_QIBUILD_DIR global variable
  and use a function instead

* Fix install of man pages

* Install qibuild html doc

* Add a quick script to test qibuild installation

* Install a qibuild-config.cmake to be able to find the qibuild framework,

* qibuild.cmake: update to version 11

include(qibuild/general) will work *only* is qibuild/general
is in CMAKE_ROOT_PATH, and we do not want to install qibuild here
(because it messes up with install rules)

so we just use a qibuild-config.cmake.

You can now use:

find_package(qibuild)

and this will work because `qibuild configure` will gently set
'qibuild_DIR` for you ;)

Changes:

* 'global' qibuild.cfg in ~/.config/qi/qibuild.cfg is no longer read

* you can now have on IDE per config

* qibuild now opt-depends on lxml, to generate pretty xml files

* merging of '-c' option, default config et all is done by the
  QiBuildConfig class instead of beeing done by Toc

* toc.update_toc_config() is gone, use
     toc.config.set....
     toc.save_config()

TODO:

* rename toc.configstore to toc.config ?

* use XML for internal storage of qitoolchain too?

(This fix automatic testing by may not be such a good idea)

Note1: the config for the project is now in
qiproject.xml, so you can use the same sources
with two versions of qibuild :)

Note2: the conversion will only happen once,
so be careful