Right. I suspect that native artifacts will have to be delineated by both
CPU architecture and OS distribution. There's generally a tight coupling
between the binary and the compiler version and glibc version and possibly
other system libraries. So the repository would need a scheme something like
${groupId}/${artifactId}/${version}/${os}/${march}. The OS would be more
specific than just "linux". I think we would need to specify a distro family
(where major versions of systems libs are fixed) like Red Hat Enterprise
Linux 3.x, Red Hat Enterprise Linux 4.x, Suse Linux Enterprise Server 9,
Fedore Core 4, etc.Roger On 11/1/05, Chris Berry <[EMAIL PROTECTED]> wrote: > > This brings up a bigger question; How does maven want to handle OS > information in the repo?? To be successful w/ other languages like C, the > repo will need to delineate information such as "i586" and "linux". Are > these to be rolled into the groupId?? That doesn't smell right. Seems that > we may need new Artifact Resolvers that understand this sort of info > natively and can transparently supply the the correct pieces to the URL. > > Cheers, > -- Chris > > On 11/1/05, dan tran <[EMAIL PROTECTED]> wrote: > > > > Hi David, > > There is a work in progress for native-maven-plugin > > http://svn.mojo.codehaus.org/trunk/mojo/maven-native/ > > You can build it and take a look at some doc. > > -Dan > > > > > > On 11/1/05, David Jackman <[EMAIL PROTECTED]> wrote: > > > > > > I've just found out that I'm going to need to expand our Maven build > > > process to include several C++ project (which I believe are built > using > > > gcc). I seem to remember seeing some traffic on this list from people > > > doing this sort of thing (which I promptly ignored because I wasn't at > > > the time). Can anyone offer some insight on how you got this to work > > > and how you overcame the problems that came up? What plugins are > > > available to build this way and do they do everything you need? Are > you > > > able to have dependencies in the Maven repository and have the build > use > > > them from there (similar to .jar dependencies)? How do you access the > > > header files, possible library, and runtime library for the different > > > portions of the build? Is there a mini guide for this kind of project > > > in the works? > > > > > > Thanks, > > > ..David.. > > > > > > > > > > > >
