> I guess at the end of the day what you are talking about is a static code
analysis tool for the CMake language. Those tools look at all possible
branches of code and try to detect errors.
What I would like to see at a minimum is a CMake Debugger showing a window
with the list of variables, not
Hello. I'm adding Haskell support to the CMake and stumbled with this
problem:
CMAKE_Haskell_COMPILE_OBJECT rule produces two files (.o itself and .hi
interface file used by haskell compiler). when i run `make clean`, all .o's
are deleted, but .hi's aren't. I've found these lines in cmake_clean.cma
On Sat, Sep 24, 2011 at 4:11 AM, Rolf Eike Beer wrote:
> Am Freitag, 23. September 2011, 16:26:46 schrieb Ben Medina:
>> Hello all,
>>
>> I'm trying to adopt greater usage of ExternalProject in my project.
>> One problem I'd like to resolve is spurious rebuilds of external
>> projects.
>
> [...]
>
Am Freitag, 23. September 2011, 16:26:46 schrieb Ben Medina:
> Hello all,
>
> I'm trying to adopt greater usage of ExternalProject in my project.
> One problem I'd like to resolve is spurious rebuilds of external
> projects.
[...]
> This works great: building "test" first untars the CLAPACK sour
