Re: Heads Up: Switch over to cmake for Qpid C++ builds
On 24 July 2013 21:35, Andrew Stitcher astitc...@redhat.com wrote: On Tue, 2013-07-23 at 20:25 +0100, Robbie Gemmell wrote: On 23 July 2013 19:46, Andrew Stitcher astitc...@redhat.com 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
Re: Heads Up: Switch over to cmake for Qpid C++ builds
On 07/23/2013 11:01 AM, Andrew Stitcher wrote: As many here will remember we introduced cmake to the C++ build process when we acquired a working Windows port courtesy of Steve Huston. At the time (the end of 2008) we discussed having 2 build systems for Qpid C++ and agreed that it was a Bad Idea. However for various reasons we are now 5 years later and we are still using both build systems. The cmake build has now (finally) come to the point of virtual parity on Unix systems and it is time to remove the autotools build. Autotools has been deprecated for a while and has been printing a warning that it will be removed soon since 0.22. 0.24 will be the last Qpid release that contains the autotools build. I will be removing all the traces of the autotools build that I know about/can find this week, so that we have the rest of the 0.25/0.26 development cycle to make sure that we haven't missed anything in the move. Hurray! Champagne for all! Let there be dancing in the streets! - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Heads Up: Switch over to cmake for Qpid C++ builds
On Tue, 2013-07-23 at 20:25 +0100, Robbie Gemmell wrote: On 23 July 2013 19:46, Andrew Stitcher astitc...@redhat.com 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 - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Heads Up: Switch over to cmake for Qpid C++ builds
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? Robbie On 23 July 2013 16:01, Andrew Stitcher astitc...@redhat.com wrote: As many here will remember we introduced cmake to the C++ build process when we acquired a working Windows port courtesy of Steve Huston. At the time (the end of 2008) we discussed having 2 build systems for Qpid C++ and agreed that it was a Bad Idea. However for various reasons we are now 5 years later and we are still using both build systems. The cmake build has now (finally) come to the point of virtual parity on Unix systems and it is time to remove the autotools build. Autotools has been deprecated for a while and has been printing a warning that it will be removed soon since 0.22. 0.24 will be the last Qpid release that contains the autotools build. I will be removing all the traces of the autotools build that I know about/can find this week, so that we have the rest of the 0.25/0.26 development cycle to make sure that we haven't missed anything in the move. Because this issue has been around so long there is more than one JIRA issue for it: The current active issue is QPID-4640 [1], there is also another similar bug QPID-3633 [2] which has a number of not yet resolved issues attached to it. If you find any problems I recommend you create a bug and link it to one (or both of these bugs) Andrew [1] https://issues.apache.org/jira/browse/QPID-4640 [2] https://issues.apache.org/jira/browse/QPID-3633 - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Heads Up: Switch over to cmake for Qpid C++ builds
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 think the answer is that we haven't, but we still have time to do this. (this step wasn't actually in the list of things that we voted for, but I agree it would be a good idea). I'll raise it a release blocking JIRA for this. Andrew - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
