[ccan] Fwd: CMake build system

Nicu Tofan nicu.tofan at gmail.com
Mon Mar 10 08:23:38 EST 2014


Hello, Emilio, thanks for your input

>
> If I may add my opinion (with weight==0), I like the current make-based
> solution, and would not like to have to maintain two separate build
> procedures.
>

I'm not proposing this as an alternate build system (but it could do that,
too). I just say that I'm using it in a CMake driven project and that it
would be way easier for anyone that wants to something like that to have
the infrastructure in place. As I said in first mail, all one has to do is
add ccan subdirectory and dependencies.

Maintaining is simple, I'd say, because CMakeLists.txt in each module is
very simple: dependencies and a one line macro call. There is one file to
maintain and that is the one in the root.

I see config.h.in as a separate issue that I would like to discuss,
because, as I said, there may be value in having a config.h.in file in each
module that lists the variables that have an effect on compilation, even if
the cmake build system is not implemented. (This is not implemented in my
fork, yet).


>
> It seems you missed the list on CCAN's official website:
>
>   http://ccodearchive.net/list.html
>

That's weird. And it is linked from main page. Thanks.

Regards,
Nicu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/ccan/attachments/20140309/b0cab950/attachment.html>


More information about the ccan mailing list