<div dir="ltr"><br><br><div class="gmail_quote">On Tue, May 22, 2012 at 1:45 AM, Eric Noulard <span dir="ltr"><<a href="mailto:eric.noulard@gmail.com" target="_blank">eric.noulard@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/5/21 Nicholas Yue <<a href="mailto:yue.nicholas@gmail.com">yue.nicholas@gmail.com</a>>:<br>
<div class="im">> Hi,<br>
><br>
> I can build debug and release code by setting the CMAKE_BUILD_TYPE<br>
> variable.<br>
><br>
> What is the recommend process/workflow if I wish to build/install/package<br>
> both the Debug and Release build into a single e.g. RPM, as part of an<br>
> automated process (e.g. nightly build) ?<br>
<br>
</div>Currently CPack cannot do that out of the box because CMake cannot do<br>
that either.<br>
CMake requires 2 build trees for that (at least on Linux)<br>
<div class="im"><br>
> How will CPack find the different builds for packaging ?<br>
<br>
</div>He won't.<br>
<br>
May be it's possible to craft your own CPackConfig.cmake file which would<br>
refer to the 2 build trees but how would you ensure that there won't<br>
be any name collision between "debug" and "release" tree?<br>
<br>
Shall they be installed in different place /prefix ?<br>
What would be the layout of the expected unique RPM ?<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Erk<br>
Le gouvernement représentatif n'est pas la démocratie --<br>
<a href="http://www.le-message.org" target="_blank">http://www.le-message.org</a><br>
</font></span><div class="HOEnZb"><div class="h5">--<br><br></div></div></blockquote><div><br>I would just compile it twice and create my-debug.rpm and my.rpm <br>Is that a viable solution for you?<br><br>Regards,<br>Kfir<br>
</div></div></div>