Cmake build

[David Delassus]

I'm currently implementing a cmake build for Cream-Browser.

I will commit it soon (maybe tonight).

The current one will not disappear. In fact I will create another project on github in order to continue the development of this nameless build system.

Why changing buildsys?
Because there is too much things to do to make it portable and powerful :
* cross compiling
* Posix shell
* Abstract makefile syntax (for gnu and bsd)
* Build out-of-tree
* etc...

And I don't want to have a commit log massively for the buildsys and not Cream-Browser itself.

A configure script will still be present in order to simplify the cmake's usage.

David Delassus

[Custom Processing Unlimited]

Good call.... keeping it as simple as possible will make it more portable and allow it to be built easily on more systems & architectures...

--
If "custom" was mass produced... it would just be a "product line."
Custom Processing Unlimited

[David Delassus]

Hi

cmake is now the default build system for Cream-Browser.
The configure script allow you to use it easily :

    $ mkdir __build__ && cd __build__
    $ ../configure --prefix=/usr --enable-mod-dummy
    cmake is running
    $ make
    # make install

It's a pure happiness :)

[Custom Processing Unlimited]

HAHA, nice!!!