Bill Hoffman wrote:
So, I did look at how to fix this some. I have a c# program that can
force a running visual studio process to close and reload the solution
it has. The idea would be to have cmake run this when cmake is run as
part of the build. However, visual studio has a neat trick
Jesper Eskilson wrote:
KSpam wrote:
If you run the ZERO_CHECK target, CMake will generate the new project
files without building everything. Following ZERO_CHECK, Visual
Studio would have to reload the projects, and then you could build
like normal. This makes building in Visual Studio
On Nov 3, 2007 6:37 AM, Alexander Neundorf [EMAIL PROTECTED] wrote:
On Thursday 01 November 2007, Brandon Van Every wrote:
On Nov 1, 2007 2:27 PM, Miguel A. Figueroa-Villanueva [EMAIL PROTECTED]
wrote:
...
Jesper,
Maybe this is a good addition to the FAQ or somewhere else in the wiki
Jesper Eskilson wrote:
Bill Hoffman wrote:
For this case, you could have something like this:
# if SOME_PROGRAM has a value but the program has been moved
# or removed from the system, then clear the cache entry
# so that find_program will try again.
if(SOME_PROGRAM AND NOT EXISTS
On Wednesday 31 October 2007, Jesper Eskilson wrote:
Bill Hoffman wrote:
For this case, you could have something like this:
# if SOME_PROGRAM has a value but the program has been moved
# or removed from the system, then clear the cache entry
# so that find_program will try again.
Andreas Pakulat wrote:
On Mittwoch, 31. Oktober 2007, Jesper Eskilson wrote:
BTW: Are there any plans of fixing the broken regeneration for Visual
Studio? Or at least documenting it as known problem? As it is now,
the project files are regenerated but not reloaded, and there is no
feedback
On 01.11.07 10:49:12, Jesper Eskilson wrote:
In any case, the automatic regeneration of project files *does* *not*
*work*, and my question was simply if there was a plan for either doing
something about it (such as disabling it per default, which would be a
sensible thing to do, IMHO), and/or
Andreas Pakulat wrote:
On 01.11.07 10:49:12, Jesper Eskilson wrote:
In any case, the automatic regeneration of project files *does* *not*
*work*, and my question was simply if there was a plan for either doing
something about it (such as disabling it per default, which would be a
sensible
On Nov 1, 2007, at 7:29 AM, Jesper Eskilson wrote:
Andreas Pakulat wrote:
On 01.11.07 10:49:12, Jesper Eskilson wrote:
In any case, the automatic regeneration of project files *does*
*not*
*work*, and my question was simply if there was a plan for either
doing
something about it (such as
On 11/1/07, Jesper Eskilson [EMAIL PROTECTED] wrote:
KSpam wrote:
If you run the ZERO_CHECK target, CMake will generate the new project files
without building everything. Following ZERO_CHECK, Visual Studio would have
to reload the projects, and then you could build like normal. This
On Nov 1, 2007 2:27 PM, Miguel A. Figueroa-Villanueva [EMAIL PROTECTED] wrote:
On 11/1/07, Jesper Eskilson [EMAIL PROTECTED] wrote:
KSpam wrote:
If you run the ZERO_CHECK target, CMake will generate the new project
files
without building everything. Following ZERO_CHECK, Visual
Hi people,
Is there a way to disable the CMake cache, i.e. prevent CMake from
generating or reading CMakeCache.txt?
--
/Jesper
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Jesper Eskilson wrote:
Hi people,
Is there a way to disable the CMake cache, i.e. prevent CMake from
generating or reading CMakeCache.txt?
No.
But, it might help more if you gave an explanation of what you are
trying to do?
-Bill
___
CMake
Jesper Eskilson wrote:
The first problem is that the Visual Studio generator fails to
properly rerun CMake when CMakeLists.txt. It reruns CMake, but the
modified projects files are not reloaded before continuing with the
build.
Unfortunately, there is no way of forcing Visual Studio to
Bill Hoffman wrote:
Jesper Eskilson wrote:
Hi people,
Is there a way to disable the CMake cache, i.e. prevent CMake from
generating or reading CMakeCache.txt?
No.
But, it might help more if you gave an explanation of what you are
trying to do?
The first problem is that the Visual
Jesper Eskilson wrote:
Bill Hoffman wrote:
Jesper Eskilson wrote:
Hi people,
Is there a way to disable the CMake cache, i.e. prevent CMake from
generating or reading CMakeCache.txt?
No.
But, it might help more if you gave an explanation of what you are
trying to do?
The first problem is
On Mittwoch, 31. Oktober 2007, Bill Hoffman wrote:
You should never have to clear out the cache.
Not quite right, what happens if I move one of the libraries to a
different place? In that case I have to at least remove all entries
that relate to that library from the cache. Not your everyday
Bill Hoffman wrote:
OK, so you want to disable the rerun of CMake, not the cache. That can
be done with the CMAKE_SUPPRESS_REGENERATION variable. (set it to TRUE).
Yes, I know how to use this variable.
You should never have to clear out the cache.
If I make a change in CMakeLists.txt
Jesper Eskilson wrote:
Bill Hoffman wrote:
OK, so you want to disable the rerun of CMake, not the cache. That
can be done with the CMAKE_SUPPRESS_REGENERATION variable. (set it to
TRUE).
Yes, I know how to use this variable.
You should never have to clear out the cache.
If I make a
Bill Hoffman wrote:
For this case, you could have something like this:
# if SOME_PROGRAM has a value but the program has been moved
# or removed from the system, then clear the cache entry
# so that find_program will try again.
if(SOME_PROGRAM AND NOT EXISTS ${SOME_PROGRAM})
set(SOME_PROGRAM
On Wednesday 31 October 2007 13:37:04 Jesper Eskilson wrote:
Ouch. My cmake files are unreadable enough without an added 3 lines here
and there checking if the cache entry needs to be replaced or not.
A custom macro or two could clean the files up quite nicely.
BTW: Are there any plans of
On Mittwoch, 31. Oktober 2007, Jesper Eskilson wrote:
BTW: Are there any plans of fixing the broken regeneration for Visual
Studio? Or at least documenting it as known problem? As it is now,
the project files are regenerated but not reloaded, and there is no
feedback that the new project files
22 matches
Mail list logo
