Re: [cmake-developers] User vs CMake include mismatch handling

2010-10-11 Thread Marcus D. Hanwell
On Sunday 10 October 2010 14:56:29 Alexander Neundorf wrote: On Friday 08 October 2010, David Cole wrote: On Fri, Oct 8, 2010 at 10:59 AM, Alexander Neundorf neund...@kde.orgwrote: ... Better idea: I'll add a policy which switches this behaviour (prefer CMAKE_ROOT over

Re: [cmake-developers] VS Plugin in 2.8.3

2010-10-11 Thread Brad King
On 10/11/2010 02:54 PM, Brad King wrote: I just tested it with the COnly test and VS9 x64. It now reloads even when the project has not changed at all (touch CMakeLists.txt). I wonder if the project solution folder feature affected this. It happens when the USE_FOLDERS property is on. The

Re: [cmake-developers] VS Plugin in 2.8.3

2010-10-11 Thread James Bigler
On Mon, Oct 11, 2010 at 2:37 PM, Brad King brad.k...@kitware.com wrote: On 10/11/2010 02:54 PM, Brad King wrote: I just tested it with the COnly test and VS9 x64. It now reloads even when the project has not changed at all (touch CMakeLists.txt). I wonder if the project solution folder

Re: [cmake-developers] User vs CMake include mismatch handling

2010-10-11 Thread Alexander Neundorf
On Monday 11 October 2010, Marcus D. Hanwell wrote: On Sunday 10 October 2010 14:56:29 Alexander Neundorf wrote: ... So is there no chance of fixing this in a backward compatible way? One of Prefering module in CMAKE_ROOT when include() or find_package() is called from CMAKE_ROOT (which does

Re: [cmake-developers] User vs CMake include mismatch handling

2010-10-11 Thread Marcus D. Hanwell
On Mon, Oct 11, 2010 at 5:00 PM, Alexander Neundorf neund...@kde.orgwrote: On Monday 11 October 2010, Marcus D. Hanwell wrote: On Sunday 10 October 2010 14:56:29 Alexander Neundorf wrote: ... So is there no chance of fixing this in a backward compatible way? One of Prefering module in