Another common scheme is to say that a version is compatible if the
major version number matches and incompatible otherwise. I'm not
saying we have to try to include every common scheme. I think just
the basic one you proposed originally is sufficient. However, I'd
like to come up with
http://public.kitware.com/Bug/view.php?id=12323 (FindDCMTK cannot find
all includes for MSVC build of DCMTK, by Dan Thill) See also my note:
http://public.kitware.com/Bug/bug_relationship_graph.php?bug_id=12323#bugnotes
Kind regards, Niels
--
Niels Dekker
http://www.xs4all.nl/~nd/dekkerware
Am Donnerstag, 28. Juli 2011, 18:49:17 schrieb David Cole:
Hi all,
Replies requested. Short replies only. Read on. Just a short reply with bug
numbers or links to the bugs is all we need here. Please move specific
discussions into the bugs themselves or start a new thread to talk about
On Jul 29, 2011, at 10:58 AM, James Sutherland wrote:
I have the following in my CMakeLists.txt:
install( DIRECTORY ${QT_PLUGINS_DIR}/imageformats
DESTINATION ${plugin_dest_dir}/plugins
COMPONENT Runtime
)
This results in the appropriate libraries (libqtiff.dylib
Hi,
So I've started bringing the matrix up to date. Just to make sure I'm not
reporting documentation-changes as real changes, please take a look at the
following items and correct me where I'm wrong:
Changes from 2.8.3 to 2.8.4:
* get_cmake_property:
previously
http://public.kitware.com/Bug/view.php?id=6493
configuration dependent COMPILE_FLAGS for SET_TARGET_PROPERTIES
http://public.kitware.com/Bug/view.php?id=6269
Some CMake commands should support Debug/Release configurations
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 4d9874440a875d59d2867216fb1037bffcc4db0a (commit)
from
