On Tue, Oct 23, 2012 at 1:07 PM, Eric Noulard <span dir="ltr"><<a href="mailto:eric.noulard@gmail.com" target="_blank">eric.noulard@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/10/23 David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>>:<br>
<div><div class="h5">> On Tue, Oct 23, 2012 at 2:53 AM, Petr Kmoch <<a href="mailto:petr.kmoch@gmail.com">petr.kmoch@gmail.com</a>> wrote:<br>
>> On Mon, Oct 22, 2012 at 4:58 PM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
>>><br>
>>> On Mon, Oct 22, 2012 at 3:22 AM, Petr Kmoch <<a href="mailto:petr.kmoch@gmail.com">petr.kmoch@gmail.com</a>> wrote:<br>
>>> > Hi Andreas,<br>
>>> ><br>
>>> > thanks for your tip. Unfortunately, 'make -k install' doesn't help, as<br>
>>> > the<br>
>>> > entire install step is a single command (cmake -P ...), so once this<br>
>>> > fails,<br>
>>> > there is no other command make could continue with. Is there no way to<br>
>>> > do<br>
>>> > this natively in cmake?<br>
>>> ><br>
>>> > I could (in theory) add OPTIONAL to all install() commands, but that has<br>
>>> > the<br>
>>> > problem of being absolutely silent when a file is not found, and I'd<br>
>>> > need at<br>
>>> > least a message or warning. Is cmake really all-or-nothing in this<br>
>>> > aspect,<br>
>>> > or does anyone know a feature I'm overlooking?<br>
>>> ><br>
>>> > Thanks for any help.<br>
>>> ><br>
>>> > Petr<br>
>>> ><br>
>>> ><br>
>>> > On Sat, Oct 20, 2012 at 12:46 PM, Andreas Pakulat <<a href="mailto:apaku@gmx.de">apaku@gmx.de</a>> wrote:<br>
>>> >><br>
>>> >> Hi,<br>
>>> >><br>
>>> >> On Sat, Oct 20, 2012 at 11:39 AM, Petr Kmoch <<a href="mailto:petr.kmoch@gmail.com">petr.kmoch@gmail.com</a>><br>
>>> >> wrote:<br>
>>> >> > when running the install step of a CMake-generated buildsystem (i.e.<br>
>>> >> > 'make<br>
>>> >> > install' or building the VS project INSTALL), the run terminates<br>
>>> >> > after<br>
>>> >> > the<br>
>>> >> > first failure (e.g. when it cannot find a file which is to be<br>
>>> >> > installed). Is<br>
>>> >> > there a way to globally change this behaviour so that the error is<br>
>>> >> > reported<br>
>>> >> > (perhaps as a warning), but the install step goes on?<br>
>>> >><br>
>>> >> For Makefile Generator you can run make -k install, that way make<br>
>>> >> keeps on going even when errors occur. No idea about VS, NMake, Ninja<br>
>>> >> or XCode generators probably depends on wether the respective tool has<br>
>>> >> a switch for continuing if errors occur.<br>
>>> >><br>
>>> >> Andreas<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > --<br>
>>> ><br>
>>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>> ><br>
>>> > Visit other Kitware open-source projects at<br>
>>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>> ><br>
>>> > Please keep messages on-topic and check the CMake FAQ at:<br>
>>> > <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
>>> ><br>
>>> > Follow this link to subscribe/unsubscribe:<br>
>>> > <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
>>><br>
>>><br>
>>> CMake is all-or-nothing with respect to an install tree. If the cmake<br>
>>> install script hits a "FATAL_ERROR" message then it stops and will not<br>
>>> continue beyond that point...<br>
>>><br>
>>> The best way to "Continue install after a failure" is to eliminate the<br>
>>> failure, and try again.<br>
>><br>
>><br>
>> Would you accept a patch giving control over this behaviour? Something like<br>
>> a boolean variable CMAKE_INSTALL_STOP_ON_ERROR (the default being TRUE, of<br>
>> course).<br>
>><br>
>> Petr<br>
><br>
> Why is patching CMake easier than fixing your project? And how long<br>
> are you going to let your own project's install tree be broken before<br>
> you do fix it?<br>
><br>
> I don't like the idea of a half-installed (or any fraction less than<br>
> 1.0) bit of software...<br>
<br>
</div></div>Me neither.<br>
<div class="im"><br>
><br>
> Perhaps others will chime in and we can get a sense of how folks weigh<br>
> in on this issue.<br>
<br>
</div>My personal opinion is that may be the only feature I'd like would be a<br>
"real fake install" i.e. 0% installed not a possibly random X percent<br>
installed with random leftover.<br>
<br>
it could be callable like:<br>
make fake-install or check-install or ... set(CMAKE_FAKE_INSTALL 1) or ...<br>
<br>
which would check whether all need-to be installed bits are accessibles.<br>
This would basically put the file(INSTALL ...) sub-command in a mode<br>
that would only check access and print-out some informations message<br>
without moving, copying or renaming any files or directory.<br>
<br>
e.g:<br>
<br>
-- Would be Up-to-date: .../share/aclocal/cmake.m4<br>
-- Would be Installing: ..../doc/cmake-2.8/cpack.html<br>
<br>
instead of<br>
-- Up-to-date: .../share/aclocal/cmake.m4<br>
-- Installing: .../doc/cmake-2.8/cpack.html<br>
<br>
That said I did live without that feature until now so I bet I can<br>
live without it forever :-]<br>
<span class="HOEnZb"><font color="#888888"></font></span><br></blockquote></div><br>We're using the install step of CMake to prepare the "installation
source" in a location where it's then picked up by a 3rd party
install-shield generator. And we're currently doing major re-structuring
of the entire installation (involving several big cooperating
products), which must work on several sites with different 3rd party
installation paths etc. Only being able to fix one error per install run
is extremely frustrating.<br><br>Eric's suggestion of a "fake install" would solve our case, of course.<br><br>I understand it's far from a typical
use case, but AFAIK, all software development tools are moving away from
"bail out on first error" to trying to report as many as possible (and
still failing at the end, if applicable).<br><br>Petr<br>