All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mnelson@redhat.com>
To: Ali Maredia <amaredia@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: Transitioning Ceph from Autotools to CMake
Date: Thu, 30 Jul 2015 14:12:08 -0500	[thread overview]
Message-ID: <55BA7708.2090300@redhat.com> (raw)
In-Reply-To: <26481727.639679.1438282888566.JavaMail.zimbra@redhat.com>

Just here to provide moral support. Go CMake go! :)

Mark

On 07/30/2015 02:01 PM, Ali Maredia wrote:
> After discussing with several other Ceph developers and Sage, I wanted
> to start a discussion about making CMake the primary build system for Ceph.
>
> CMake works just fine as it is (make -j4 on master with CMake builds
> 350% faster than autotools!), but there's more work needed to make it
> into a first-class build system.
>
> Short term (1-2 weeks):
>   - Making sure CMake works on all supported platforms: Centos7, RHEL7,
>     Ubuntu 14.04 & 12.04, Fedora 22, Debian Jessie, Debian Wheezy are the
>     target platforms I have noted to test on already.
>   - Adding a target similar to make check
>   - Creating CMake targets that build packages (such as for rpm or debian)
>   - Writing documentation for those who haven't used CMake before to smooth the
>     transition over
>   - Making sure no targets or dependencies are missing from the
>     current CMake build, and that CMake supports all current
>     targets, configurations and options
>   - Replacing the integration autotools has with any automated build/test
>     systems such as the gitbuilder
>
> Longer term (2-4 weeks):
>   - Removing the current autotools files, to avoid doubling build system
>     workload
>   - Adding more but shorter CMakeLists.txt files to a tree like structure
>     where a CMakeLists.txt would be in every subdirectory
>
> I'm already working on a target similar to the make check target, and plan
> on working on the other short term goals over the next weeks and beyond.
>
> I wanted to get feedback from the community any reasons why someone started using
> CMake but stopped (ex: lack of functionality), and more broadly, on what other
> obstacles there might be for the transition.
>
> -Ali
> --
> 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
>

  reply	other threads:[~2015-07-30 19:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <568775149.634533.1438280976401.JavaMail.zimbra@redhat.com>
2015-07-30 19:01 ` Transitioning Ceph from Autotools to CMake Ali Maredia
2015-07-30 19:12   ` Mark Nelson [this message]
2015-07-30 19:34   ` Ken Dreyer
2015-08-01 19:24   ` Orit Wasserman
2015-08-03 10:09     ` John Spray
2015-08-03 23:38       ` John Spray
2015-08-05 11:14         ` Orit Wasserman
2015-08-04 10:42   ` Owen Synge
2015-08-04 18:26     ` Ali Maredia
2015-08-05 12:43       ` Owen Synge

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=55BA7708.2090300@redhat.com \
    --to=mnelson@redhat.com \
    --cc=amaredia@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    /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.