Ivy is built for Java and its jars. By default, Ivy uses the Maven worldwide repository system to search for jars. It also is built for Ant integration.
However, you could emulate this structure if you use your own Maven/Ivy style repository such as Nexus or Artifactory. You'll have to figure out a naming convention thats similar to Ivy's and Maven's (organisation/groupID, name/artifactId, revision/version), and disconnect your Nexus/Artifactory repository from the rest of the world since if the artifact isn't in your repository, you don't want to look in the Maven worldwide repository system. You could also build `build.xml` files for Ant just to download the needed library objects (*.dll, *.o, *.so, , *.a, etc.) using <ivy:resolve>. There will be some work involved, but I've seen people do this. However, there might be better tools. For example, BuildBoost: http://www.boost.org/boost-build2/index.html. I never used it, but I've heard it talked about as a Maven for C++ projects. On Dec 6, 2012, at 10:15 AM, Marcel Overdijk <[email protected]> wrote: > > I wonder if somebody has some pointers for using Ivy in a C/C++ environment. > > a) how is dependency management done (e.g. using custom resolver?) > b) how is building done (based on on de Ivy dependencies) > > > I'm not looking for a complete solution, just wat to start a discussion > about possibilities or perhaps best practices from people already having > this set up. > > Unfortunately I can't find and information in the docs. Ivy is especially > interesting as it is nog tight to Java dependency management. > > > > > > -- > View this message in context: > http://old.nabble.com/Ivy-in-C-C%2B%2B-environment-tp34767076p34767076.html > Sent from the ivy-user mailing list archive at Nabble.com. >
