Return-Path: X-Original-To: apmail-ant-ivy-user-archive@www.apache.org Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 89DA8E0AD for ; Fri, 7 Dec 2012 07:55:53 +0000 (UTC) Received: (qmail 23285 invoked by uid 500); 7 Dec 2012 07:55:52 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 23260 invoked by uid 500); 7 Dec 2012 07:55:52 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 23212 invoked by uid 99); 7 Dec 2012 07:55:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2012 07:55:51 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Dec 2012 07:55:46 +0000 Received: from telerig.nabble.com ([192.168.236.162]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TgsmM-0001dt-6R for ivy-user@ant.apache.org; Thu, 06 Dec 2012 23:55:26 -0800 Message-ID: <34769838.post@talk.nabble.com> Date: Thu, 6 Dec 2012 23:55:26 -0800 (PST) From: Marcel Overdijk To: ivy-user@ant.apache.org Subject: Re: Ivy in C/C++ environment In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: marceloverdijk@gmail.com References: <34767076.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Yes this is exactly our idea. To just use Ivy / Ant resolve/download the the needed (transitive) dependencies and unpack zip's if needed. >From there on we can make 'native' builds. David Weintraub wrote: > > 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 . 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 > 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. >> > > > -- View this message in context: http://old.nabble.com/Ivy-in-C-C%2B%2B-environment-tp34767076p34769838.html Sent from the ivy-user mailing list archive at Nabble.com.