On 6/28/07, Ken Martin <[EMAIL PROTECTED]> wrote:
CMake can get above 100% (or other screwy situations) in a couple odd cases,
such as killing an install done as root half way through, and then doing a
build as non-root. Basically it uses some files for tracking progress and if
they get written by root and left there (like in an aborted install) then
the user account cannot clean them out. Another case is if you do two builds
in the same tree from different processes (not a parallel build using -j 2,
but two different make invocations in the same tree) This can also happen if
you invoke a "make" in the tree as part of a custom rule within the build.
e.g. you do a recusrive make on your own as part of a custom rule. They are
odd cases but they could happen. I'll try adding some more error checking
for those cases at some point.
But more specifically for your case, what target are you making? The all
target from the top level?
Yep.
Is there a /CMakeFIles/Progress directory still lying around?
Yes there is. It has only 1 line: CMAKE_ALL_PROGRESS = 72. I'll try
rebuilding from scratch and seeing what happens.
Are you running just one make?
Just one.
Does chicken do a recusrise
make/build as part of a custom command (e.g. invoke make directly as part of
a custom command?)
No recursive make. Some "cmake -P" scripts are invoked though.
Another weird thing I do is reuse object files from a previous build
step, so that I don't have to include the same underlying library 6
times.
Cheers,
Brandon Van Every
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
