From: Brad Hubbard <bhubbard@redhat.com>
To: Willem Jan Withagen <wjw@digiware.nl>
Cc: Sage Weil <sweil@redhat.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: cmake
Date: Mon, 4 Jul 2016 20:37:15 +1000 [thread overview]
Message-ID: <CAF-wwdEA+hjDa3mAZXp8jNEn_1c1-9RUzBqaVTaKBFXO0bWpOg@mail.gmail.com> (raw)
In-Reply-To: <0ba08c31-8c9e-a483-6c5b-07ce9b6b5495@digiware.nl>
On Mon, Jul 4, 2016 at 7:05 PM, Willem Jan Withagen <wjw@digiware.nl> wrote:
> On 27-6-2016 19:50, 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.
>
> Hi Sage,
>
> Question about Cmake versions....
>
> On FreeBSD cmake is version 3.5.2
> My Centos box has 2.8.11
>
> If there any "minimum" requirements here??
You should be fine.
[ceph] (master %)$ head -1 CMakeLists.txt
cmake_minimum_required(VERSION 2.8.11)
HTH,
Brad
>
> --WjW
>
>
>
> --
> 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
--
Cheers,
Brad
next prev parent reply other threads:[~2016-07-04 10:37 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 ` cmake Mark Nelson
2016-07-04 9:05 ` cmake Willem Jan Withagen
2016-07-04 10:37 ` Brad Hubbard [this message]
-- 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=CAF-wwdEA+hjDa3mAZXp8jNEn_1c1-9RUzBqaVTaKBFXO0bWpOg@mail.gmail.com \
--to=bhubbard@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@redhat.com \
--cc=wjw@digiware.nl \
/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.