<div dir="ltr"><div class="gmail_default" style="font-family:times new roman,serif;font-size:small"><span style="font-family:arial,sans-serif">On Sat, Oct 10, 2015 at 4:49 PM, Haïkel </span><span dir="ltr" style="font-family:arial,sans-serif"><<a href="mailto:hguemar@fedoraproject.org" target="_blank">hguemar@fedoraproject.org</a>></span><span style="font-family:arial,sans-serif"> wrote:</span><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">2015-10-10 22:25 GMT+02:00 Neal Gompa <<a href="mailto:ngompa13@gmail.com">ngompa13@gmail.com</a>>:<br>
> Hello all,<br>
><br>
> Over the last few weeks, I've been working on a number of packages that use<br>
> CMake for the build system for various distros, and I've noticed something<br>
> rather peculiar. Of all the distros I've built packages for (Fedora/CentOS,<br>
> openSUSE, Mageia, Debian, and Ubuntu), only Fedora/CentOS does not<br>
> automatically do CMake building in a subdirectory such that the build<br>
> artifacts don't mix in with the source tree. Essentially, the %cmake macro<br>
> doesn't enforce builds are out-of-tree.<br>
><br>
> Is there a particular reason for this?<br>
><br>
<br>
</span>According Rex who implemented the %cmake macro<br>
<a href="https://www.redhat.com/archives/fedora-packaging/2007-March/msg00044.html" rel="noreferrer" target="_blank">https://www.redhat.com/archives/fedora-packaging/2007-March/msg00044.html</a><br>
<br>
I must admit that I agree that out-of-tree builds is not very useful<br>
in RPM packaging case, as you always scratch the build directory.<br>
Implementing out-of-tree builds who result in having to move between<br>
directories during package building which could error-prone.<br>
<br>
Regards,<br>
H.<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote></div><br><div class="gmail_default" style="font-family:'times new roman',serif;font-size:small">It has come up for me as somewhat problematic, as when builds fail, it's hard to tell what happened to the generated and pristine data, because it seems quite a few of these make the assumption it is going to be out of tree and happily do things that make no sense for in-source builds. What's worse, at least one of them doesn't even implement a proper install target, so that makes things somewhat challenging.</div><div class="gmail_default" style="font-family:'times new roman',serif;font-size:small"><br></div><div class="gmail_default" style="font-family:'times new roman',serif;font-size:small">At the end of the day, it's just strange to me that our CMake building is in-source instead of out of source, since the whole <i>point</i> of CMake in the first place is to be used for out-of-source builds.</div><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">真実はいつも一つ！/ Always, there's only one truth!<br></div></div>
</div><font face="yw-402608bc37fe50adb11a5899295781aeb83d248d-e0f0dadca5ec43393c6c5320cac6110e--o" style="display: none;"></font></div>