On Tue, Jan 4, 2011 at 7:51 AM, Rolf Eike Beer <e...@sf-mail.de> wrote:
>> On Tue, Jan 4, 2011 at 6:58 AM, Andrea Galeazzi <galea...@korg.it> wrote:
>>> I'm currently dealing with a project requiring a lot of dependencies
>>> (74),
>>> so the structure of the CMakeLists.txt is as following:
>>> project ( Main )
>>> add_subdirectory("W:/Lib1" "${CMAKE_CURRENT_BINARY_DIR}/Lib1")
>>> add_subdirectory("W:/Lib2" "${CMAKE_CURRENT_BINARY_DIR}/Lib2")
>>> add_subdirectory("W:/Lib3" "${CMAKE_CURRENT_BINARY_DIR}/Lib3")
>>> ................
>>> add_executable( Main ${SOURCES} )
>>> target_link_libraries(Main ${LIB_TO_LINK})
>>>
>>> When I choose a VS2010 CMake generates a solution of 77 projects (74
>>> +Main
>>> + ALL_BUILD + ZERO_CHECK).
>>> Now if I modify the CMakeLists.txt of one of the subproject and build
>>> the
>>> Main project VS2010 notify that many other project has been modified and
>>> also the solution. So, for instance, if I add a file to a subproject
>>> VS2010
>>> shows a lot of dialog asking to reload the projects again and that's
>>> very
>>> frustrating!
>>> My question is: is it a bug or a normal behavior? If the second, how can
>>> I
>>> avoid it?
>
>> It's listed as a bug in the CMake bug tracker:
>> http://public.kitware.com/Bug/view.php?id=11258
>
> [...]
>
>> For now the best workaround (that I personally use all the time), is
>> to exit Visual Studio entirely, run cmake or cmake-gui manually, and
>> then re-launch Visual Studio. It may sound painful, but really, it's
>> much more enjoyable than wading through all the reload dialogs...
>
> Isn't it enough to unload the solution? That would save at least the time
> starting Visual Studio.
>
> Eike
> _______________________________________________
> 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
>
Yes, simply unloading the solution (rather than fully exiting Visual
Studio) also appears to be adequate.
I've found that 2nd and subsequent launches of VS are not nearly as
painful as the initial launch. Sometimes you get into an overkill
habit that's hard to unlearn later on... :-)
_______________________________________________
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
