Re: [CMake] CMake for Python 3

2013-03-25 Thread Eric Noulard
2013/3/25 Pietro Moras > > I'd love to be reassured that CMake (+CPack) is a “right” tool for: > >Building the distribution package for a complex Python 3 (+PyQt) > application, mainly aimed at the Windows platform. If your application is pure python why would you use CMake instead of pure py

Re: [CMake] Disabling Argument Parsing in CMake -P Scripts

2013-03-25 Thread Gregoire Aujay
Hello, I would be interested in the '--' to disable command line argument parsing by CMake. Has someone opened an issue on mantis for this one ? Regards, Gregoire -Original Message- From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of David Cole Sent: samedi 3

[CMake] CMake for Python 3

2013-03-25 Thread Pietro Moras
I'd love to be reassured that CMake (+CPack) is a “right” tool for: Building the distribution package for a complex Python 3 (+PyQt) application, mainly aimed at the Windows platform. My goal is a single install file that, out of an original Python 3 application, will generate an ordinary “.exe”

Re: [CMake] add_test() and DEBUG_POSTFIX

2013-03-25 Thread David Cole
If you use the NAME/COMMAND signature form of add_test, the COMMAND may be a target name, and if it doesn't "just work" at that point, it is a bug. Also, for multi-config generators, you may need to use -C Release or -C Debug on the ctest command line to run the correct configuration. On Mar 2

Re: [CMake] add_test() and DEBUG_POSTFIX

2013-03-25 Thread Nils Gladitz
The second parameter to add_test is an executable name (it may be a script or executable which may not even be build by cmake) rather than a target name so I'd say this is by design. Nils On 03/25/2013 02:15 PM, Martin Baute wrote: I did not get any feedback on this, so please excuse me askin

Re: [CMake] add_test() and DEBUG_POSTFIX

2013-03-25 Thread Martin Baute
I did not get any feedback on this, so please excuse me asking again: Is it by design that adding a DEBUG_POSTFIX to executables makes CMake miss those very same executables when running "make test"? It is a bit awkward having to chose between either: A) having no postfix with executables, i.e.

Re: [CMake] Explicit _LIBRARIES and _INCLUDE_DIRS

2013-03-25 Thread Mateusz Loskot
On 23 March 2013 14:29, Alexander Neundorf wrote: > On Friday 22 March 2013, Mateusz Loskot wrote: >> On 22 March 2013 18:01, Sergei Nikulov wrote: >> > 2013/3/22 Mateusz Loskot >> > >> >> I'm trying to build software which uses libE57 library which has >> >> Xerces as dependency. >> >> I build