All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Dreyer <kdreyer@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 13:34:26 -0600	[thread overview]
Message-ID: <55BA7C42.4020404@redhat.com> (raw)
In-Reply-To: <26481727.639679.1438282888566.JavaMail.zimbra@redhat.com>

On 07/30/2015 01:01 PM, Ali Maredia wrote:
>  - Creating CMake targets that build packages (such as for rpm or debian)

There was some discussion on the list a while back about how we don't
really need to go through the full autoconf + ./configure + "make rpm"
routine simply to generate packages with the right version information.
My conclusion was that we should be able to generate a release tarball
(and even SRPM or RPM) with a shell script, rather than trying to do it
in autotools with a make target.

The reasoning was speed and efficiency: there's no point to running
"./configure" to generate an SRPM when the RPM itself runs "./configure"
during its build.

I don't know how well this maps to CMake, and whether CMake gives you
some sort of "skip everything and immediately do <foo>"... clearly I
need to learn more about CMake :)

>  - Replacing the integration autotools has with any automated build/test
>    systems such as the gitbuilder

We hope to eventually replace gitbuilder with something more scalable
like Jenkins, but in the meantime we're maintaining both systems :(

gitbuilder is https://github.com/ceph/autobuild-ceph
Jenkins is https://github.com/ceph/ceph-build

And then Loic also runs a make check bot in his own Jenkins instance.

  parent reply	other threads:[~2015-07-30 19:34 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
2015-07-30 19:34   ` Ken Dreyer [this message]
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=55BA7C42.4020404@redhat.com \
    --to=kdreyer@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.