On 24 July 2013 21:35, Andrew Stitcher <[email protected]> wrote:

> On Tue, 2013-07-23 at 20:25 +0100, Robbie Gemmell wrote:
> > On 23 July 2013 19:46, Andrew Stitcher <[email protected]> wrote:
> >
> > > On Tue, 2013-07-23 at 17:13 +0100, Robbie Gemmell wrote:
> > > > It was announced on the user list before 0.22 that we would disable
> the
> > > > automake build by default for 0.24 so that users had to explicitly
> enable
> > > > it (as many people dont read logs for builds which seem to complete
> ok
> > > and
> > > > might miss the deprecation notice), and would thus definitely know
> it was
> > > > being removed entirely in 0.26. Is that happening?
> > >
> > > I must have my fuzzy head on today - I'm sorry I can't parse the
> > > question at the end there.
> > >
> > > Are you asking whether we have disabled autotools by default in 0.24?
> >
> >
> > I was asking if we are planning to do so, as originally said back around
> > March. I know we haven't done it yet as the Jenkins jobs are still using
> it
> > :)
>
> Well, I'd expect the Jenkins trunk jobs to stop working pretty soon now!
> First from requiring the option, then in short order because the entire
> build system has gone!
>
> I don't think Carl has given me credentials yet to help you migrate to
> cmake, do you know any better?
>
> Andrew
>
>
It did indeed fail. I added the new configure option and scheduled a build,
we shall see if that temporarily fixes it (if i did it right :P) once it
gets run.

I havent had a chance to lok at moving it to cmake myself, and I dont know
of any way I can tell whether you have access yet (have you tried logging
in again and seeing if you get the build and configure etc buttons/options
yet?).

Robbie

Reply via email to