Charles,
I'd like to comment on a minor issue:
CMakeLists.txt files don't specify user-specific data like source and build
dirs (for a reason) yet your POC listfile contains this line:
cmake.init("Ninja", "/media/dev/src/cmaketest",
"/media/dev/build/cmaketest")
which sets the source and
I took the time to make it work again, so I pushed it here:
https://github.com/packadal/CMake/tree/cmake-python
The whole branch is ugly as can be, and because I started with an old CMake
and recently rebased, the python abstraction might be bloated already, but
it works in the nominal case, and
Yes, this is POC-only.
I felt too lazy to make an argparse object and properly perform these tasks.
Obviously, the generator and source dir should be arguments.
The build dir should be the execution dir of the script, to mimic CMake
behavior.
This should not be difficult, but as I said I wanted
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=15901
==
Reported By:acgtyrant
Assigned To:
Hi Brad,
To round off the -W options functionality, I've implemented the -Werror
and -Wno-error set of options for the two current types of messages, dev
and deprecated. This includes updating the QT GUI to include new options
for controlling this functionality.
The third patch is not for
The following issue has been SUBMITTED.
==
https://public.kitware.com/Bug/view.php?id=15902
==
Reported By:iainmeikle
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=15903
==
Reported By:Bernd Lörwald
Assigned To:
On Sun, Dec 27, 2015 at 22:04:14 +0100, Dimitar Yordanov wrote:
> I agree with you. Running valgrind directly on the cmake binary
> provides useful information: I can see which internal cmake functions
> are used the most and consume most of the time.
>
> Nevertheless, I think it would be useful
