On 6/10/2014 11:30 AM, Stephen Kelly wrote:
I think
http://sscce.org/
explains is quite well.
I want to avoid having to understand all of the ParaView CMake code and that
of its dependencies, and whether python bindings need to be enabled etc.
The real problem is that we need to have some regression tests in CMake
that test for these types of performance issues. Right now we don't
have them. Creating a SSCCE for the issues we are seeing would be doing
just that.
However, right now we know there are issues with ParaView. It might
not be too much to ask for you to give it a quick try. I am sure Ben
could give you the -D options for CMake since ParaView is pretty self
contained. I think basically building ParaView with Python wrapping
shows the issue. So, you will need python installed and they
Ben, can you run your timing test with a commit before my topic and after
it? Timing tests with master and your extra topics don't tell us anything on
this question.
Do you think you could try ParaView and if you run into trouble give up
on it. However, I would hope it would involve a git clone, and a
cmake -DPARAVIEW_ENABLE_PYTHON=TRUE ../ParaViewSrc
In the mean time, I will see if we can work on trying to create some
better regression tests for CMake performance.
Thanks.
-Bill
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
