Hi Alan,
Personally I'd rather cmake was given the heave ho ;->

for all of it's pain automake is something of a defacto standard for a ton of projects.

Re "Anyone know of specific issues that need to be addressed in cmake?" yeah, I don't have cmake installed :-D sorry. I'm just messing.

Seriously though I've just reached a point with 0.20 where I didn't have to hack around with things to get Qpid to compile on my Ubuntu box, so if I'm honest I'm a little disinclined to change something that finally works to have things potentially break more again.

If there are strong feelings that agree with your view to move to cmake can I suggest that deprecation rather than removal of automake is announced. I think just deleting it from 0.22 is a bit draconian and I think we should have a couple of releases at least where both exist but one is marked deprecated so that users get a chance to flag up where things break (plenty of users only work off official releases - imagine their surprise if they are forced to use cmake and either they don't have cmake installed or the cmake breaks for them).

I'm clearly biased 'cause I haven't used cmake, but I'm very anti just deleting the automake build without a period of it being properly deprecated.

All that said I do have sympathy with the view that having two build systems is probably not ideal.

Oh and to follow on a thread that was started a little while back by Gordon I *really* think that this proposal should be flagged up on the qpid users mailing list too!!

Frase


On 08/03/13 14:56, Alan Conway wrote:
Having 2 build systems is a waste of time and a source of confusion. We introduced the cmake build with the intent that it would replace the automake system, I think the time has come to say farewell to automake. The cmake system is ready: it covers the same ground as automake and more (esp. windows), and it is actively and successfully used by many developers.

I propose that once we have branched for the 0.22 release, we delete the automake build system. That will give us plenty of time to find and fix any issues with the cmake system before the next release. I'm not aware of any major deficiencies in the cmake system, minor discrepancies will be quickly found and fixed once everyone has switched. I volunteer to help resolve issues that come up.

Are there any strong opinions out there for or against? Anyone know of specific issues that need to be addressed in cmake?

Cheers,
Alan.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to