<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>You're right. Normally I do not ignore errors, but in some situations if unit tests and/or parts of new libraries are under development, on some platforms they won't compile/link, but the main application is still stable and could be packaged. I think you know what I mean. It is not my decision.</div><div><br></div><div><div style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">How could I overwrite it?</div></div><div><br></div><div><br>Am 06.02.2013 um 20:23 schrieb David Cole <<a href="mailto:dlrdave@aol.com">dlrdave@aol.com</a>>:<br><br></div><blockquote type="cite"><div><font color="black" size="2" face="arial"><font size="2">My advice to you would <font size="2">be not to ignore the errors.<br>
<br>
<font size="2">If you want to i<font size="2">gnore them anyway, you're on your own. Or maybe somebody else who is also ignoring errors like these will s<font size="2">tep up with some alternate advice. </font>;-)</font></font><br>
</font></font></font><font color="black" face="arial" size="2">
</font><div><font color="black" face="arial" size="2"> <br>
<font size="2">You can <font size="2">o<font size="2">verride what CPack calls for "make install" -- <font size="2">you can tell it to run something else that won't do a "make all" first.</font></font></font></font></font> But it <font size="2">would probably be easier to just fix the errors.</font><br>
</div>
<div> <br>
<br>
<font size="2"><font size="2">D<br>
<br>
</font></font>
</div>
<div> <br>
</div>
<div style="font-family:arial,helvetica;font-size:10pt;color:black"><font color="black" face="arial" size="2">-----Original Message-----<br>
From: NoRulez <<a href="mailto:norulez@me.com">norulez@me.com</a>><br>
To: David Cole <<a href="mailto:dlrdave@aol.com">dlrdave@aol.com</a>><br>
Cc: eric.noulard <<a href="mailto:eric.noulard@gmail.com">eric.noulard@gmail.com</a>>; cmake <<a href="mailto:cmake@cmake.org">cmake@cmake.org</a>><br>
Sent: Wed, Feb 6, 2013 2:19 pm<br>
Subject: Re: [CMake] Running CPack and ignore exit codes<br>
<br>
</font>
<div id="AOLMsgPart_1_2fde2055-0b9f-4b5f-8e96-a504c3f8006c"><font color="black" face="arial" size="2">
<div>Ok, when I have the following situation:</div>
<div><br>
</div>
<div>prj1 (install target)</div>
<div>prj2 (not install target but produce compile error, so this could be ignored)</div>
<div>prj3 <span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">(install target)</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">prj4 (</span><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">install target)</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><br>
</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">At the moment I call "cpack -G ZIP" (normally I call cpack from within a CTestScript) and it stops by prj2 without building the zip archive.</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">If the prj2 doesn't have errors it runs smoothly.</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><br>
</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Did this mean that I must know (at CTestScript time) which projects should be build?</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">e.g.: cpack -G ZIP prj1 prj2 prj3?</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><br>
</span></div>
<div><span style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">Best Regards</span></div>
<div><br>
</div>
<div>Am 06.02.2013 um 19:58 schrieb David Cole <<a href="mailto:dlrdave@aol.com">dlrdave@aol.com</a>>:<br>
<br>
</div>
<div><span></span></div>
</font><blockquote type="cite"><font color="black" face="arial" size="2">
</font>
<div><font color="black" face="arial" size="2"><font color="black" face="arial" size="2">CPack does call "make install"<font size="2"> -- and make install first doe<font size="2">s a make all to get everything up to date.....<br>
<br>
<font size="2">So even calling just cpack by <font size="2">its<font size="2">elf in this situation is no good.</font></font></font><br>
</font></font></font></font><font color="black" face="arial" size="2">
<div> <br>
</div>
<div> <br>
</div>
<div> <br>
</div>
<div style="font-family:arial,helvetica;font-size:10pt;color:black">-----Original Message-----<br>
From: Eric Noulard <<a href="mailto:eric.noulard@gmail.com">eric.noulard@gmail.com</a>><br>
To: NoRulez <<a href="mailto:norulez@me.com">norulez@me.com</a>><br>
Cc: CMake ML <<a href="mailto:cmake@cmake.org">cmake@cmake.org</a>><br>
Sent: Wed, Feb 6, 2013 1:57 pm<br>
Subject: Re: [CMake] Running CPack and ignore exit codes<br>
<br>
<div id="AOLMsgPart_0_3fbc84b6-f28a-44d6-8ddd-b4ae9b79c5f3" style="margin: 0px;font-family: Tahoma, Verdana, Arial, Sans-Serif;font-size: 12px;color: #000;background-color: #fff;">
<pre style="font-size: 9pt;"><tt>2013/2/6 NoRulez <<a href="mailto:norulez@me.com">norulez@me.com</a>>:
> Because CPack runs the default (all) target.
Ok now I think I get it.
AIFAIK, CPack does NOT run "all" target.
"make package" does.
You should be able to call CPack explicitely without problem, try:
cpack
in your build dir. However this won't try to build anything.
> It could be that a target doesn't build because of compile or link errors and
are not an install target (unit tests for example or other sub projects which
are not required).
You'll build a package with a failing unit test !! :-]
> CPack should build as much as possible and only break if an install target has
errors.
Like I said, CPack does not build anything per se, the "package"
target depends on "all"
so that the build tool (make, Visual Studio, XCode etc...) does build all.
> Currently it is not possible to run cpack and create packages for such
situation.
True but I'm not sure I would personnally want to build a package out
of a partially buildable project.
Other may have other opinion though.
From my point of view, if you really want to accept the building of a
package even if
some target may fail then you could simply make the building of those
targets optional
using
option(BUILD_OPTIONAL_TARGET "Build Optional Target" OFF)
then
if(BUILD_OPTIONAL_TARGET)
add_executable(...)
endif()
Then set BUILD_OPTIONAL_TARGET to OFF if you don't care of those when
building a package.
Currently CMake (and not CPack) is not tracking down target that
"are built but not installed"
it may be doable but this would be a new feature.
I don't really know the portion of CMake code handling manifest files
but AFAIRemember this was handled **at install time** so that the
list of "to be installed files/target" is unknown at CMake time.
What "may be possible" is to add a new "package/fast" target
which would depend on "preinstall/fast and install/fast" instead of
"preinstall" so that
you will avoid the build of "all"
The trouble is, the fast target does not build **anything** so you'll
have to do:
make -k all
make package/fast
to achieve what you want.
--
Erk
Le gouvernement représentatif n'est pas la démocratie --
<a target="_blank" href="http://www.le-message.org">http://www.le-message.org</a>
--
Powered by <a target="_blank" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a target="_blank" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Please keep messages on-topic and check the CMake FAQ at: <a target="_blank" href="http://www.cmake.org/Wiki/CMake_FAQ">http://www.cmake.org/Wiki/CMake_FAQ</a>
Follow this link to subscribe/unsubscribe:
<a target="_blank" href="http://www.cmake.org/mailman/listinfo/cmake">http://www.cmake.org/mailman/listinfo/cmake</a>
</tt></pre>
</div>
</div>
</font></div>
</blockquote>
</div>
<!-- end of AOLMsgPart_1_2fde2055-0b9f-4b5f-8e96-a504c3f8006c -->
</div>
</div></blockquote></body></html>