[CMake] Workflow of a collaborative project in Visual Studio+CMake

[Clifford Yapp]

That's what we do to.

It basically comes down to the inconvenience of having to do that with
Visual Studio being outweighed (considerably!) by the cross-platform
benefits of CMake.  (It does help that none of our developers use Windows
as their primary development platform, so it only comes up when we make
sure things are working on Windows...)

I really wish Microsoft would integrate support for CMake projects into
Visual Studio the way KDevelop has, although I suppose that's right up
there probability wise with hoping they'll integrate clang...

Cheers,
CY

On Sat, Nov 12, 2011 at 7:39 AM, David Cole <david.cole at kitware.com> wrote:

> For reference, the bug Mike refers to is this one:
>
>  http://public.kitware.com/Bug/view.php?id=11258
>
> I always use the manual technique of shutting down VS, running CMake,
> and then re-opening VS. It's really not that bad, once you get used to
> it.
>
>
> David C.
>
>
> On Fri, Nov 11, 2011 at 5:48 PM, Michael Jackson
> <mike.jackson at bluequartz.net> wrote:
> > It is worse and better.
> >
> > 1: CMake will generate the VS projects and solutions every time it needs
> to run. DO NOT EDIT the generated VS projects and solutions. Add the
> requirements to the CMake files.
> >
> > 2: If you are on VS2007/VS2008 and you do a "git pull" and then switch
> to VS and click build a cmake check is run FIRST. If anything is different
> the new solution and project files are generated and then the build
> continues. You will get a dialog asking if you want to reload all of the
> projects. Things are pretty nice.
> >
> > 3: If you are on VS2010 there is now a long standing bug that seems to
> have no solution where you basically have to do the following:
> >  Close the VS solution
> >  git pull
> >  run cmake to regenerate the solution and projects
> >  Open the Solution and Compile.
> >
> > Yep. Sucks. Purchased VS2010 last year and have yet to use it because of
> that bug. If we (the cmake community**) were to actually figure out how to
> solve the problem then VS2010 would be as seamless as VS2008. Here is
> hoping for the future.
> >
> > ** I have kept track of the bug. Kitware and others have put a lot of
> time into trying to fix the bug. It just seams to be one of those elusive
> fixes that there just may not be a solution to.
> > --
> > Mike Jackson <www.bluequartz.net>
> >
> > On Nov 11, 2011, at 5:30 PM, David Doria wrote:
> >
> >> I typically work in KDevelop which has CMake support, so if another
> >> developer pushes some new files and changes to the CMakeLists.txt of
> >> my project, I simply 'git pull' the project and then click "Build" and
> >> it knows exactly what to do - it runs CMake and then builds the
> >> project.
> >>
> >> However, when working with Visual Studio, do I have to 'git pull',
> >> then go open cmake-gui from the VS2010E terminal, re-configure and
> >> re-generate the project, then reimport the VS2010E project, then
> >> build? This seems horribly awkward. And the reverse appears to have
> >> the same problem - if working inside VS I add a file to the VS
> >> project, how do I 'export' this addition back to the git repo?
> >>
> >> Thanks,
> >>
> >> David
> >> --
> >
> > --
> >
> > 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
> >
> --
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20111112/39f9d96b/attachment.htm>