From: Mark Nelson <mnelson@redhat.com>
To: Casey Bodley <cbodley@redhat.com>, Sage Weil <sweil@redhat.com>,
ceph-devel@vger.kernel.org
Subject: Re: cmake
Date: Tue, 28 Jun 2016 16:43:57 -0500 [thread overview]
Message-ID: <4c5c008f-ad0a-bcb5-7faa-d9971d42ba61@redhat.com> (raw)
In-Reply-To: <29a3fbd4-8659-1391-79ce-98a37e5b84c8@redhat.com>
On 06/28/2016 03:28 PM, Casey Bodley wrote:
>
> On 06/27/2016 01:50 PM, Sage Weil wrote:
>> We are switching from autotools to cmake on the master branch. Any
>> builds done post-jewel will be cmake and not autotools based. Jewel and
>> older releases will still be built with autotools the old way.
>>
>> The README.md in the master branch has been updated with new developer
>> build instructions. Please take a look:
>>
>> https://github.com/ceph/ceph/blob/master/README.md
>>
>> If you are doing development, please switch to using cmake (i.e.,
>> run do_cmake.sh) now. Running vstart.sh is a little different and it
>> takes some getting used to.
>>
>> If there is anything that doesn't work that is part of your developer
>> workflow, we need to fix it now, before the autotools support is removed
>> and you're unable to work! This is hopefully a week or two away.
>>
>> Current status:
>>
>> - gitbuilders mostly using make-dist instead of 'make dist'
>> (autotools) to generate release tarballs
>> - wip-cmake-debian building debs with cmake
>> - rpm coming shortly
>> - release build tool update last, followed by a 11.0.0 release.
>>
>> Thank you!
>> sage
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> To those trying CMake, please note that autoconf generates a
> ceph/src/acconfig.h. You'll want to remove that header, or cmake builds
> will pull it in and get confused.
>
> Build failures in rocksdb are also common for those switching. This
> seems to fix those issues: cd ceph/src/rocksdb; make clean
FWIW, this is a gotcha that folks using automake run into when the
rocksdb submodule updates. make clean; make top level doesn't fix it,
you have to explicitly run make clean in the rocksdb directory.
>
> Casey
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-06-28 21:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Mark Nelson [this message]
2016-07-04 9:05 ` cmake Willem Jan Withagen
2016-07-04 10:37 ` cmake Brad Hubbard
-- strict thread matches above, loose matches on Subject: below --
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 ` cmake Willem Jan Withagen
2015-12-16 23:36 ` cmake Willem Jan Withagen
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
2009-04-01 17:35 cmake Shane Dixon
2009-04-02 5:30 ` cmake Jeremy Lainé
2009-04-02 16:44 ` cmake Otavio Salvador
2009-04-02 18:07 ` cmake Koen Kooi
2009-04-02 17:07 ` cmake Robert Schuster
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=4c5c008f-ad0a-bcb5-7faa-d9971d42ba61@redhat.com \
--to=mnelson@redhat.com \
--cc=cbodley@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.