[Rivet] Force rivet to use its own yaml-cpp

[David Hall]

Hi David,

Thanks for your help. I suppose rivet 2.0 will suffer from future changes to the yaml-cpp API then? Hopefully its more stable now.

You're suggestion makes the build possible, but is not quite working. When I 'make install' it tries to overwrite the existing header files in /usr/local/include/yaml-cpp

Now I could just leave those uninstalled, but then other programs that build with rivet (e.g. Herwig++) might struggle to build, right? I know I could install with a different prefix, but I'm trying to avoid that.

Any suggestions?

Thanks,
David


On 28 May 2013, at 16:12, David Grellscheid <david.grellscheid at durham.ac.uk> wrote:

> Hi David,
> 
> Not directly at the moment, but this issue is almost gone. The 2.0 series of Rivet will not have a built-in copy of YAML, so will use a system version. One thing you could try is to set --with-yaml_cpp to a path that does not exist. I.e.
> 
> ./configure ..... --with-yaml_cpp=/foo/bar/not/here
> 
> See you,
> 
>  David
> 
> On 28/05/2013 15:57, David Hall wrote:
>> Hi,
>> 
>> I was wondering if there is a way, during the configuration, to force rivet to use its own yaml-cpp installation. The problem is that if a recent version of yaml-cpp is already installed in /usr/local then autotools will find this and the build will fail (since the API is not backward compatible).
>> 
>> Thanks,
>> David
>> 
>> _______________________________________________
>> Rivet mailing list
>> Rivet at projects.hepforge.org
>> http://www.hepforge.org/lists/listinfo/rivet
>>