What do you mean? I don't know what the proton devs would need to do to support cmake -- the deliverables would be the same regardless of the build system, or can be made to be identical.
On Mon, Jul 23, 2012 at 11:20 AM, Steve Huston <[email protected]> wrote: > Forgive my naiveté wrt Maven, but Qpid C++ currently uses cmake (and > autoconf, but that's got a limited lifespan). It would be nice to limit > the number of build systems we need to maintain. I know proton is not > Qpid, but the knowledge and setups needed is one more thing C++ devs would > need to take care of if working on proton. Is there any support on the > proton devs part of using cmake for the C++ part? > > -Steve > > On 7/23/12 9:41 AM, "Joseph Ottinger" <[email protected]> wrote: > >>I was wondering if it'd be valuable to convert the build for proton to >>maven. It's not a "rocket surgery" conversion - it involves moving >>files and just a touch of configuration - but at the same time, >>there're a lot of benefits. >> >>For better or for worse, there're two dominant build systems in Java; >>one is Ant, the other Maven. Maven is winning, because Ant's not >>*really* a build system - it's a scripting engine that people use for >>builds, while Maven is a build system for realz, yo. Maven means a >>regular lifecycle for the build, including explicit testing, >>packaging, distribution phases; ant allows those things but doesn't >>help you create them, and Maven has standards for them. >> >>Maven's set of tools is also very useful; again, you can do the same >>things with Ant if you try, but few developers really care a lot about >>having done stuff in the build system. They'd rather focus on the >>project, not the build. With Maven, we can slap Arquillian into the >>build (for example) and have a full module/integration/system test as >>part of the build process, instead of bolting such things into place. >> >>Maven's also cross-language. Proton isn't just Java, of course; Maven >>means we can use C++ and still have only one build process (within >>certain reason; I'm not claiming Maven's the equivalent of autoconf, >>because duh, but then again, autoconf is SOOOOO much fun....) >> >>I'm more than willing to convert the build over if desired; the java >>part's already done, I'd still need to do the C++ conversion but it >>would be pretty easy. >>-- >>Joseph B. Ottinger >>http://enigmastation.com >>Ça en vaut la peine. >> >>--------------------------------------------------------------------- >>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] > -- Joseph B. Ottinger http://enigmastation.com Ça en vaut la peine. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
