Hi Nick, Tyler,
Another option is to pass the names of the lists to the macro (one for
the CPP files, one for the XML files), instead of their contents. You
would then need a ${${...}} construct to get their values.
The (only) downside to that solution is that you cannot pass literal
string argu
On Monday 06 July 2009, Nick Davidson wrote:
> Dear List,
>
> Is there an idomatic way of converting an implicit makefile rule to a
> CMakeLists construct?
> Currently I'm resorting to writing a macro which processes list
> variables with foreach and adds various linked custom targets but I'm
> fin
On Mon, Jul 06, 2009 at 06:07:11PM +0100, Nick Davidson wrote:
> macro (MakeCustomTarget TARGET_FILE CPP XML)
> add_custom_target(TARGET_FILE ALL
> COMMAND process ${TARGET_FILE} ${CPP}
> COMMAND process ${TARGET_FILE} ${XML})
> message(STATUS "Cannot find xgettext")
>
Dear List,
Is there an idomatic way of converting an implicit makefile rule to a
CMakeLists construct?
Currently I'm resorting to writing a macro which processes list
variables with foreach and adds various linked custom targets but I'm
finding lots of confusion when passing lists as arguments to
