Managing 3rd party dependencies for C++

[Scott Palmer]

On 2012-04-17, at 11:26 AM, Hylton Peimer wrote:

> We have to parallel development groups.
>  
> One group uses Java with Maven, and the maven manages dependencies with a local Sonatype Nexus repository.
>  
> The C++ team also have many third party libraries which need to be managed. Since moving to HG we used subrepository feature of hg to bring the third party libraries from an SVN repository.  Previous solution used SVN externals.  SVN’s advantage here is that we don’t have to fetch the entire repository, instead only bring the required version in the .hgsub
>  
> This solution is clumsy. Especially updating and adding new versions.
>  
> Are there alternative solutions for managing third party C++ libs with Mercurial, on Windows.

We use Maven for C++ stuff too.
We zip third party assets (SDKs) and publish them to a Maven repository (Artifactory) and have a pom that fetches and unzips what is needed for the C++ build.  We have also experimented with using Gradle to both publish and fetch build artifacts with the same asset repository, as I don't particularly like the inflexible and tedious nature of Maven.

Scott

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20120417/7fcc69bd/attachment-0002.html>