On 19/12/12 16:21, David Cole wrote:
No need for specific examples. Just wanted to understand the context
better.
One good way to avoid this warning would be to get your Find* script
changes into CMake itself, and then eliminate your need for the custom
copies of them when using a new-enough
On 19/12/12 17:56, David Cole wrote:
I think the safest/wisest thing to do in this case is to update your
minimum required version to CMake 2.8.4, and then adjust your custom
code to eliminate the warning if it still occurs.
2.8.4 is more than 18 months old at this point. Is there a reason why
On Wednesday, December 19, 2012 01:18:47 PM Daniel Russel wrote:
> I'm using the shipped UseSWIG package to add a swig module to my project
> (cmake 2.8). For those that don't know, swig works by running the swig
> command on an input file (a .i) and then building the files that it
> produces. The
I'm using the shipped UseSWIG package to add a swig module to my project (cmake
2.8). For those that don't know, swig works by running the swig command on an
input file (a .i) and then building the files that it produces. The input file
tells swig to scan certain header files and the output file
I think the safest/wisest thing to do in this case is to update your
minimum required version to CMake 2.8.4, and then adjust your custom code
to eliminate the warning if it still occurs.
2.8.4 is more than 18 months old at this point. Is there a reason why 2.6.2
is still required for some?
On W
On Wednesday 19 December 2012, Marcel Loose wrote:
> Hi David,
>
> I need to set a policy to OLD, because I have wrapped a few existing
> Find*.cmake files to overcome some bugs or shortcomings. However, since
> CMake 2.8.4 (or 2.8.3, I'm not sure), this triggers a policy warning
> CMP0017 with ne
No need for specific examples. Just wanted to understand the context better.
One good way to avoid this warning would be to get your Find* script
changes into CMake itself, and then eliminate your need for the custom
copies of them when using a new-enough CMake.
Is it feasible for you to propose
Stephen Kelly wrote:
> Note that an RC1 was released in the mean-time:
>
> http://qt-project.org/downloads
>
> That does not change anything with regard to the CMake files however.
Qt 5.0 final has now been released :).
http://blog.qt.digia.com/blog/2012/12/19/qt-5-0/
It also does not chang
Hi David,
I need to set a policy to OLD, because I have wrapped a few existing
Find*.cmake files to overcome some bugs or shortcomings. However, since
CMake 2.8.4 (or 2.8.3, I'm not sure), this triggers a policy warning
CMP0017 with newer versions of CMake, because some macros are now
include
Op 18-12-12 13:46, David Cole schreef:
On Mon, Dec 17, 2012 at 11:57 AM, Alexander Neundorf
mailto:a.neundorf-w...@gmx.net>> wrote:
On Monday 17 December 2012, David Cole wrote:
> I thought we wanted them to switch to the new behavior... Isn't
that the
> goal of emitting warning
10 matches
Mail list logo