Thank you very much for pointing out the Jade Native Plugin for building native C/C++ applications with Maven<http://www.jfrog.org/sites/jade-plugins/1.3/jade-plugin-parent/jade-build-plugin-parent/jade-native-plugin/index.html>. As you observe in the nabble thread, the mojo maven-native-plugin is quite weak. Freehep's Maven plugin for native builds<http://java.freehep.org/freehep-nar-plugin/>entails overhead to enable multiple-architecture targets and distributable libraries which will not help my current project.
I'm undecided about rewriting the makefiles vs switching to Maven. The advantage of rewriting makefiles is that it will be relatively easy to do incrementally. I had hoped that the Maven plugins would provide a level of conventional defaults similar to Java development. As it stands, the Maven approach with Jade looks like it may require about as much explicit code as a makefile. Time to start some experiments... On Thu, Mar 5, 2009 at 5:49 AM, Rémy Sanlaville <[email protected]>wrote: > Hi John, > > I am not aware of such of archetype(s) but it will be nice if some could be > available. > > Nevertheless, it exists specific plugin for C/C++ language. > Cf. > http://n2.nabble.com/Maven-2-and-C-C%2B%2B-Testing-Framework-tt2416084.html > > I am interested by your experiment in maven 2 and C language. > > Rémy > >
