Re: [CMake] [cmake-developers] CMake 2.8.12-rc1 Released

2013-08-26 Thread Brad King
On 08/22/2013 04:39 PM, Alexander Neundorf wrote: > Beside that, I played around with it a bit. > If 2.8.12 is required, it errors out, as documented. > > If I use 2.8.12 and require 2.8.11: [snip] > So this seems to behave differently than in 2.8.11 even if 2.8.11 is required > (and so the polic

Re: [CMake] [cmake-developers] CMake 2.8.12-rc1 Released

2013-08-22 Thread Alexander Neundorf
On Thursday 22 August 2013, Stephen Kelly wrote: > Alexander Neundorf wrote: > > On Tuesday 20 August 2013, Robert Maynard wrote: > >> Introduced CMake Policy 21: > >> It is now an error to use relative paths to include_directories. > > > > Why is this necessary ? > > The documentation for this

Re: [CMake] [cmake-developers] CMake 2.8.12-rc1 Released

2013-08-22 Thread Robert Maynard
Stephen is correct the issue is with the incorrect release notes that I made. I will be updating the blog post with the corrected text, and will make the change is included for all future 2.8.12 releases. On Thu, Aug 22, 2013 at 3:09 AM, Stephen Kelly wrote: > Alexander Neundorf wrote: > >> >> On

Re: [CMake] [cmake-developers] CMake 2.8.12-rc1 Released

2013-08-22 Thread Stephen Kelly
Alexander Neundorf wrote: > > On Tuesday 20 August 2013, Robert Maynard wrote: >> Introduced CMake Policy 21: >> It is now an error to use relative paths to include_directories. > > Why is this necessary ? > The documentation for this policy says: > "The base path for such relative entries is

Re: [CMake] [cmake-developers] CMake 2.8.12-rc1 Released

2013-08-21 Thread Alexander Neundorf
On Tuesday 20 August 2013, Robert Maynard wrote: > Introduced CMake Policy 21: > It is now an error to use relative paths to include_directories. Why is this necessary ? The documentation for this policy says: "The base path for such relative entries is not well defined." I don't understand t