[Dune] using cmake to build your dune module

[Carsten Gräser]

Am 07.12.2010 09:46, schrieb Oliver Sander:
> I still think it would be convenient to have duneproject create
> dune modules with a cmake build system instead of the AutoTools one.
> Maybe there is a volunteer who is willing to attempt a patch?
Currently one essential part is still missing:

In the how-to cmake is only used to replace automake
while autoconf/configure is still needed to do the
tests. Before implementing this in duneproject
we should also use cmake for testing.

But don't get me wrong: Having this how-to is really nice
and it might serve as starting point to develop this.

> Anyways, thanks for the text.  It provides the dune-developer-
> with-no-experience-in-cmake-yet with an idea of what 'switching to
> cmake' actually means.

Best
Carsten

> 
> best,
> Oliver
> 
> Am 06.12.2010 19:08, schrieb Felix Albrecht:
>> Hi,
>>
>> On Mon, 2010-12-06 at 18:03 +0100, Sascha Zelzer wrote:
>>   
>>> I am wondering if the set of files is complete, since in CMakeLists.txt,
>>> variables like ALL_PKG_CPPFLAGS and DUNEMPICPPFLAGS are used but never
>>> defined.
>>>      
>> as far as i know, these variables should not have to be set by the user,
>> but rather be provided by e.g. dunecontrol.
>>
>>   
>>> Further, the macors HEADERCHECK and ADD_DUNE_EXECUTABLE in
>>> DuneUtils.cmake are never called (ADD_DUNE_EXECUTABLE wouldn't work
>>> because it depends on cmake/regen_config_header.sh).
>>>      
>> DuneUtils.cmake is a collection of macros that could be useful, although
>> some of them may not be used in my example. I have used HEADERCHECK and
>> it works.
>> ADD_DUNE_EXECUTABLE is a leftover which I will remove, you should use
>> ADD_EXECUTABLE instead. If you have further suggestions, just write me.
>>
>> Greetings,
>>
>> Felix