From: Willem Jan Withagen <wjw@digiware.nl>
To: Sage Weil <sweil@redhat.com>, Matt Benjamin <mbenjamin@redhat.com>
Cc: Yehuda Sadeh-Weinraub <yehuda@redhat.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: cmake
Date: Thu, 17 Dec 2015 00:47:48 +0100 [thread overview]
Message-ID: <5671F824.3070408@digiware.nl> (raw)
In-Reply-To: <alpine.DEB.2.00.1512161136490.10312@cobra.newdream.net>
On 16-12-2015 20:38, Sage Weil wrote:
> On Wed, 16 Dec 2015, Matt Benjamin wrote:
>> I'm going to push for cmake work already in progress to be moved to the
>> next milestone ASAP.
>>
>> With respect to "make check" blockers, which contains the issue of where
>> cmake puts built objects. Ali, Casey, and I discussed this today at
>> some length. We think the current "hackery" to make cmake make check
>> work "the same way" auto* did is long-term undesirable due to it
>> mutating files in the src dir. I have not assumed that it would be an
>> improvement to put all objects built in a tree of submakes into a single
>> dir, as automake does. I do think it is essential that at least
>> eventually, it makes it simple to operate on any object that is built,
>> and simple to extend processes like make check.
>
> All of the binaries eventually go into /usr[/local]/bin anyway. Can we
> do the same here? (I don't care where intermediate .lo or .o objects
> go...)
Why not take it one step further and have something like:
..../ceph/build/{bin,sbin,lib,libexec,etc,tmp,test,log,.....}
which would be separate tree part where all the stuff is build.
Cleaning up will then also become a lot easier.... ATM the stuff in .lib
is not cleaned, I think.
It would also allow to process scripts to fit the local OS by running it
thru m4/sed/awk/perl/...
Or if you prefer so, hang it of ..../ceph/src
But then again this might require something like: make install-build
--WjW
next prev parent reply other threads:[~2015-12-16 23:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 17:33 cmake Sage Weil
2015-12-16 17:53 ` cmake Loic Dachary
2015-12-16 18:28 ` cmake John Spray
2015-12-16 19:36 ` cmake Sage Weil
2015-12-16 18:45 ` cmake Yehuda Sadeh-Weinraub
2015-12-16 19:06 ` cmake Matt Benjamin
2015-12-16 19:38 ` cmake Sage Weil
2015-12-16 23:47 ` Willem Jan Withagen [this message]
2015-12-16 23:36 ` cmake Willem Jan Withagen
-- strict thread matches above, loose matches on Subject: below --
2016-06-27 17:50 cmake Sage Weil
2016-06-28 7:35 ` cmake Willem Jan Withagen
2016-06-28 8:41 ` cmake Willem Jan Withagen
2016-06-28 8:57 ` cmake Willem Jan Withagen
2016-06-28 13:42 ` cmake Sage Weil
2016-06-28 16:05 ` cmake Willem Jan Withagen
2016-06-29 16:51 ` cmake Willem Jan Withagen
2016-06-30 19:03 ` cmake Willem Jan Withagen
2016-07-05 19:09 ` cmake Willem Jan Withagen
2016-06-28 20:28 ` cmake Casey Bodley
2016-06-28 21:43 ` cmake Mark Nelson
2016-07-04 9:05 ` cmake Willem Jan Withagen
2016-07-04 10:37 ` cmake Brad Hubbard
2015-12-03 22:24 cmake Pete Zaitcev
2015-12-03 22:30 ` cmake Adam C. Emerson
2015-12-04 0:03 ` cmake Pete Zaitcev
2015-12-04 0:26 ` cmake Matt Benjamin
2015-12-04 8:59 ` cmake Pete Zaitcev
2015-12-04 14:15 ` cmake Daniel Gryniewicz
2015-12-03 22:30 ` cmake Matt Benjamin
2015-12-03 22:31 ` cmake Matt Benjamin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5671F824.3070408@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=mbenjamin@redhat.com \
--cc=sweil@redhat.com \
--cc=yehuda@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox