Well, my thought wasn't necessarily to replace cmake for the non-Java parts - Maven is *capable* of doing non-Java-based builds, but isn't necessarily idiomatic. I'd think using Maven for C++ builds would be a little pathological, honestly - doable but not necessarily profitable.
For Java, it'd be worthwhile; for C++, using Cmake is probably wisest. On Mon, Jul 23, 2012 at 11:45 AM, Steve Huston <[email protected]> wrote: > (In my best Rosanna Roasanna-danna imitation) Oh - never mind. > > Thanks, > -Steve > > On 7/23/12 11:45 AM, "Rafael Schloming" <[email protected]> wrote: > >>On Mon, 2012-07-23 at 15:20 +0000, Steve Huston 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? >> >>We already do use cmake for the C part (there is currently no C++ code). >> >>--Rafael >> >> >> >>--------------------------------------------------------------------- >>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]
