[CMake] Visual Studio macro execution inconsistency

Robert Dailey rcdailey.lists at gmail.com
Thu Nov 15 17:34:40 EST 2012


Thanks David.

I read through the whole thing and it's unfortunate that such a
problem even exists. A typical macro won't work, because of the issues
you noted about Build.Cancel. vscommands has no support for IDEs older
than VS10 it seems, so that won't work for me (I'm still using VS9).
The only thing left to try is a native plugin, which would have to be
installed with CMake. You'd probably have to build a separate one for
each IDE. A native plugin was suggested in the bug discussion; has no
one tried that yet?

On Thu, Nov 15, 2012 at 1:53 PM, David Cole <david.cole at kitware.com> wrote:
> We intentionally did that, by design, with the assumption that people
> would be working from the root solution file most of the time.
>
> This is the first time, to my knowledge, anybody has made this
> particular complaint to the mailing list.
>
> It would be possible to itearate the full list of generated solution
> files and make reload calls for each one that happens to be open.....
> but somebody would have to write the code to do that: it's just time
> and effort, (plus, it doesn't work well with VS10 and later anyhow...
> see http://public.kitware.com/Bug/view.php?id=11258 (sad, but I know
> this bug number by heart now))
>
> I'd recommend using the non-CMake solution to this problem mentioned
> in that bug report if possible. Try using the VS plugin from
> vscommands.com and see if it works better for you.
>
>
> HTH,
> David
>
>
>
> On Thu, Nov 15, 2012 at 2:31 PM, Robert Dailey <rcdailey.lists at gmail.com> wrote:
>> Any info on this?
>>
>> On Tue, Nov 6, 2012 at 5:58 PM, Robert Dailey <rcdailey.lists at gmail.com> wrote:
>>> There is a macro installed into Visual Studio 2008 by CMake that
>>> detects when the solution & projects have been regenerated and will
>>> allow me to reload the solution without clicking through hundreds of
>>> individual reload confirmations for each project.
>>>
>>> I find that this macro works fine if I work directly from the solution
>>> generated by the top-level project() command (in the root
>>> CMakeLists.txt script), however it does not work for any solutions I
>>> use further down the output directory tree from other project() calls.
>>>
>>> When I work from these other solutions, CMake is successfully invoked
>>> when scripts are changed, but I do not get any confirmation to reload
>>> the solution from the macro.
>>>
>>> Any reason why this doesn't work? Is it a problem on my end, or is
>>> this a known issue?
>> --
>>
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake


More information about the CMake mailing list