On 01/13/2012 08:02 PM, Michael Hertling wrote:
On 01/13/2012 03:42 PM, Bill Hoffman wrote:
On 1/13/2012 9:10 AM, Michael Hertling wrote:
With CMake 2.8.7 and VS 2008, I can report the following findings:
(1) Starting out from within an empty build directory: cmake ..
followed by cmake
...@cmake.org] On Behalf
Of Michael Hertling
Sent: Thursday, February 09, 2012 8:52 AM
To: cmake@cmake.org
Subject: Re: [CMake] MSBuild and automatic project file regenation
On 01/13/2012 08:02 PM, Michael Hertling wrote:
On 01/13/2012 03:42 PM, Bill Hoffman wrote:
On 1/13/2012 9:10 AM, Michael
I took a look at this, and it is behaving as expected with VS. VS does
NOT have a depend on compile flags. You can change a .vcproj file and
the flags it uses all you want, and VS will NOT rebuild any files
because of that.
So, as far as VS is concerned your source file has not changed and
On 01/10/2012 07:09 PM, Óscar Fuentes wrote:
Michael Hertling mhertl...@online.de
writes:
But aren't the issues related at least?
Dunno.
If I understand
correctly, cmake --build invokes MSBuild which
- loads the solution file and the project files,
- reinvokes CMake via the
On 1/13/2012 9:10 AM, Michael Hertling wrote:
With CMake 2.8.7 and VS 2008, I can report the following findings:
(1) Starting out from within an empty build directory: cmake ..
followed by cmake --build . configures/builds as expected.
(2) Tweaking CMakeLists.txt file only and leaving
On 01/13/2012 03:42 PM, Bill Hoffman wrote:
On 1/13/2012 9:10 AM, Michael Hertling wrote:
With CMake 2.8.7 and VS 2008, I can report the following findings:
(1) Starting out from within an empty build directory: cmake ..
followed by cmake --build . configures/builds as expected.
(2)
Michael Hertling mhertl...@online.de
writes:
But aren't the issues related at least?
Dunno.
If I understand
correctly, cmake --build invokes MSBuild which
- loads the solution file and the project files,
- reinvokes CMake via the ZERO_CHECK project/target
to regenerate them if
On Sun, Jan 8, 2012 at 11:59 PM, Óscar Fuentes o...@wanadoo.es wrote:
When MSBuild.exe is used (typically by cmake --build) for building a
VS2010 project generated by cmake, it correctly invokes cmake for
regenerating the project files if changes to the CMakeLists.txt files
are detected.
On 01/09/2012 02:34 PM, David Cole wrote:
On Sun, Jan 8, 2012 at 11:59 PM, Óscar Fuentes o...@wanadoo.es wrote:
When MSBuild.exe is used (typically by cmake --build) for building a
VS2010 project generated by cmake, it correctly invokes cmake for
regenerating the project files if changes to
Michael Hertling mhertl...@online.de
writes:
On 01/09/2012 02:34 PM, David Cole wrote:
No trick, but to avoid this, perhaps we should change the --build
handler to run the cmake configure generate step before calling out
to MSBuild. You can easily do this yourself from the command line by
On Mon, Jan 9, 2012 at 1:56 PM, Óscar Fuentes o...@wanadoo.es wrote:
Michael Hertling mhertl...@online.de
writes:
On 01/09/2012 02:34 PM, David Cole wrote:
No trick, but to avoid this, perhaps we should change the --build
handler to run the cmake configure generate step before calling out
On 01/09/2012 07:56 PM, Óscar Fuentes wrote:
Michael Hertling mhertl...@online.de
writes:
On 01/09/2012 02:34 PM, David Cole wrote:
No trick, but to avoid this, perhaps we should change the --build
handler to run the cmake configure generate step before calling out
to MSBuild. You can
When MSBuild.exe is used (typically by cmake --build) for building a
VS2010 project generated by cmake, it correctly invokes cmake for
regenerating the project files if changes to the CMakeLists.txt files
are detected. However, the build does not restart nor abort, so MSBuild
continues using the
13 matches
Mail list logo
