[CMake] custom target (kernel modules)

[Clark J. Wang]

On 6/29/07, Alexandru Ciobanu <aciobanu at matrox.com> wrote:
>
> Hi, Clark!
>
> Here is the reason why I wanted to use this approach.
>
> I use ADD_CUSTOM_COMMAND and ADD_CUSTOM_TARGET because I don't want
> to run that Makefile at all if the files did not change.
>
> ADD_CUSTOM_TARGET with ALL parameter would always run make. And even if
> there
> are no modifications to the source files, you'll see something like this
> on the screen:
>    [make] I've been in that dir
>    [make] nothing to do there
>    [make] all targets ok, leaving, I'm done, etc..
> And this will appear every time you build.
>
> I don't want that on my screen. It strains my eyes. I want a clean
> output. =)
>
> When combined, the above commands, always try to build the target, but
> run make
> only when needed -> no extra stuff on the screen (unless modifications
> detected).


 Thanks, Alex.

Alex Ciobanu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/cmake/attachments/20070630/5cfbf44d/attachment.htm