You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Andrew Stitcher <as...@redhat.com> on 2011/11/11 16:53:25 UTC
Remove autotools? [Was: Problems building trunk cpp broker since
this morning - `src/qmf2.pc.in' not found]
On Fri, 2011-11-11 at 15:24 +0000, Robbie Gemmell wrote:
> This kind of thing seems like a good reason to add a CMake build
> project to Jenkins (or, you know, just have 1 build system :p) in
> addition to the autotools build Keith set up. Any takers?
Personally I go for the 1 build system - Cmake.
At present Cmake is very nearly at parity with autotools (given the
recent work I checked in from Jan-Marek Glogowski) and I'd say it would
be feasible (given the available time) to remove autotools and shift to
cmake in the 0.16 time frame.
I think the only remaining work is to make the tests on cmake be at
parity with autotools.
[There's also tidying work we should do, because neither of the build
systems is very pretty or very maintainable at this point, but having
just one would help a lot]
Andrew
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: Remove autotools? [Was: Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found]
Posted by Steve Huston <sh...@riverace.com>.
+20 :-)
> -----Original Message-----
> From: Cliff Jansen [mailto:cliffjansen@gmail.com]
> Sent: Friday, November 11, 2011 12:02 PM
> To: dev@qpid.apache.org
> Subject: Re: Remove autotools? [Was: Problems building trunk cpp broker
> since this morning - `src/qmf2.pc.in' not found]
>
> +1
>
> An additional sub-task would be to rework the separate powershell and sh
> scripts within cmake/ctest to a single base (python is a likely
candidate), so
> that contributers don't need to wear multiple hats.
>
> On Fri, Nov 11, 2011 at 7:53 AM, Andrew Stitcher <as...@redhat.com>
> wrote:
> > On Fri, 2011-11-11 at 15:24 +0000, Robbie Gemmell wrote:
> >> This kind of thing seems like a good reason to add a CMake build
> >> project to Jenkins (or, you know, just have 1 build system :p) in
> >> addition to the autotools build Keith set up. Any takers?
> >
> > Personally I go for the 1 build system - Cmake.
> >
> > At present Cmake is very nearly at parity with autotools (given the
> > recent work I checked in from Jan-Marek Glogowski) and I'd say it
> > would be feasible (given the available time) to remove autotools and
> > shift to cmake in the 0.16 time frame.
> >
> > I think the only remaining work is to make the tests on cmake be at
> > parity with autotools.
> >
> > [There's also tidying work we should do, because neither of the build
> > systems is very pretty or very maintainable at this point, but having
> > just one would help a lot]
> >
> > Andrew
> >
> >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Remove autotools? [Was: Problems building trunk cpp broker since
this morning - `src/qmf2.pc.in' not found]
Posted by Cliff Jansen <cl...@gmail.com>.
+1
An additional sub-task would be to rework the separate powershell and
sh scripts within cmake/ctest to a single base (python is a likely
candidate), so that contributers don't need to wear multiple hats.
On Fri, Nov 11, 2011 at 7:53 AM, Andrew Stitcher <as...@redhat.com> wrote:
> On Fri, 2011-11-11 at 15:24 +0000, Robbie Gemmell wrote:
>> This kind of thing seems like a good reason to add a CMake build
>> project to Jenkins (or, you know, just have 1 build system :p) in
>> addition to the autotools build Keith set up. Any takers?
>
> Personally I go for the 1 build system - Cmake.
>
> At present Cmake is very nearly at parity with autotools (given the
> recent work I checked in from Jan-Marek Glogowski) and I'd say it would
> be feasible (given the available time) to remove autotools and shift to
> cmake in the 0.16 time frame.
>
> I think the only remaining work is to make the tests on cmake be at
> parity with autotools.
>
> [There's also tidying work we should do, because neither of the build
> systems is very pretty or very maintainable at this point, but having
> just one would help a lot]
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: Remove autotools? [Was: Problems building trunk cpp broker since
this morning - `src/qmf2.pc.in' not found]
Posted by Alan Conway <ac...@redhat.com>.
+1
On 11/11/2011 10:53 AM, Andrew Stitcher wrote:
> On Fri, 2011-11-11 at 15:24 +0000, Robbie Gemmell wrote:
>> This kind of thing seems like a good reason to add a CMake build
>> project to Jenkins (or, you know, just have 1 build system :p) in
>> addition to the autotools build Keith set up. Any takers?
>
> Personally I go for the 1 build system - Cmake.
>
> At present Cmake is very nearly at parity with autotools (given the
> recent work I checked in from Jan-Marek Glogowski) and I'd say it would
> be feasible (given the available time) to remove autotools and shift to
> cmake in the 0.16 time frame.
>
> I think the only remaining work is to make the tests on cmake be at
> parity with autotools.
>
> [There's also tidying work we should do, because neither of the build
> systems is very pretty or very maintainable at this point, but having
> just one would help a lot]
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org