Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of qazwart@gmail.com designates
 209.85.161.173 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Ivy in C/C++ environment
From: David Weintraub <qazwart@gmail.com>
In-Reply-To: <34767076.post@talk.nabble.com>
Date: Thu, 6 Dec 2012 11:06:55 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E375F197-0BDD-471C-A400-610BF9DC114B@gmail.com>
References: <34767076.post@talk.nabble.com>
To: ivy-user@ant.apache.org

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 <marceloverdijk@gmail.com> =
wrote:

>=20
> I wonder if somebody has some pointers for using Ivy in a C/C++ =
environment.
>=20
> a) how is dependency management done (e.g. using custom resolver?)
> b) how is building done (based on on de Ivy dependencies)
>=20
>=20
> 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.
>=20
> Unfortunately I can't find and information in the docs. Ivy is =
especially
> interesting as it is nog tight to Java dependency management.
>=20
>=20
>=20
>=20
>=20
> --=20
> View this message in context: =
http://old.nabble.com/Ivy-in-C-C%2B%2B-environment-tp34767076p34767076.htm=
l
> Sent from the ivy-user mailing list archive at Nabble.com.
>=20