On 11/12/2011 01:39 PM, David Cole 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
>
On Nov 12, 2011, at 11:08 AM, Bill Hoffman wrote:
> On 11/12/2011 10:51 AM, John Drescher wrote:
>>> 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 o
On Sat, Nov 12, 2011 at 11:08 AM, Bill Hoffman wrote:
> On 11/12/2011 10:51 AM, John Drescher wrote:
>>>
>>> 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 no
On 11/12/2011 10:51 AM, John Drescher wrote:
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,
> 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
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 whe
On 12 November 2011 12:39, David Cole 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
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, Micha
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
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 wor
10 matches
Mail list logo
