- Original Message -
I noticed today that the UseQt4 module appends a lot of different data
to the COMPILE_DEFINITIONS property via add_definitions but appends
only one item to various COMPILE_DEFINITIONS_CONFIG properties.
Is this a bug in the UseQt4 module?
I don't think that is
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14642
==
Reported By:philrosenberg
Assigned To:
clin...@elemtech.com wrote:
These situations is why I like the target usage requirements, which could
make UseQt4.cmake, or perhaps any Use*.cmake obsolete.
http://community.kde.org/Frameworks/Epics/CMake_target_usage_requirements
I've just pushed a branch fixing a minor issue in
On 2013-11-22 15:49, Brad King wrote:
On 11/22/2013 03:24 PM, Matthew Woehlke wrote:
In particular, I am wondering if it is possible, and if so, what
recommendations there are if any, to document functions 'doxygen style',
i.e. the documentation immediately preceding the function definitions,
On 2013-11-22 15:49, Brad King wrote:
On 11/22/2013 03:24 PM, Matthew Woehlke wrote:
In particular, I am wondering if it is possible, and if so, what
recommendations there are if any, to document functions 'doxygen style',
i.e. the documentation immediately preceding the function definitions,
The following issue has been SUBMITTED.
==
http://cmake.org/Bug/view.php?id=14643
==
Reported By:Clinton Stimpson
Assigned To:
2013/12/6 Rolf Eike Beer e...@sf-mail.de:
Hi,
I noticed that the message backtrace facility detected in default set of
libraries appears every time CMake is run, and not just when the library is
searched for, which is not what the modules usually do. Can this be changed?
It took a bit more
