Re: Ivy in C/C++ environment

Ivy isn't really built just for Java, its system of dependencies and artifacts are content agnostic. The community is pretty Java-focused and, it's true, there are some built-in features that are Java-centric, such as Maven integration, and those make it easy to work in a Java environment, but

Re: Ivy in C/C++ environment

I love Ivy and use it a lot, but I agree with Archie, probably CMake + rpm/deb is going to be much more effective for C/C++ than trying to build an Ant/Ivy solution. Alan On 12/7/2012 7:51 AM, Archie Cobbs wrote: The C/C++ world does have a de-facto standard for dependency management and buil

Re: Ivy in C/C++ environment

The C/C++ world does have a de-facto standard for dependency management and builds. It's called RPM (or .deb, etc.). For example, check out the openSUSE build service. You have a pile of C/C++ code and need to define dependency meta-data? OK, then create an RPM spec fi

Re: Ivy in C/C++ environment

One of the nice things about Ivy is that it works with your current build mechanism. You don't have to redo everything from scratch. I see the power of Maven. However, converting 100 Ant projects into Maven instead of using Ivy is asking for trouble. The main issue is that there doesn't seem t

RE: Ivy in C/C++ environment

Martin, As we are also looking for alternatives that are a better fit, we are also considering Gradle. Gradle also has an experimental C++ plugin: http://gradle.org/docs/current/userguide/cpp.html Something like this in theory it would mean you can use Gradle for both dependency resolving and bui