[Rivet] boost.m4 BOOST_FIND_LIB

[James Monk]

Hi Andy,

There's a new branch called "gzip" with the iostreams dependency.  I don't understand why, but it's also put the jet tagging stuff into the default branch rather than on its own branch as it was on my repository - I merged the trunk onto the jet-tagging, but I guess this meant there was only a single tip?  Will this fix itself the next time someone pushes into the repo?

There's also something annoying going on with m4/libtool.m4 and pyext directory.  Those were generated by my local build, and I actually don't know why they are in the repository at all!

cheers,

James


On 12 Jul 2013, at 18:57, Andy Buckley wrote:

> Yeah, a branch for now, please. I'm desperate to get 2.0.0 out asap, and
> that means minimising any possible build system etc. headaches! After
> that we can start being more demanding/adventurous.
> 
> Andy
> 
> 
> On 12/07/13 17:51, James Monk wrote:
>> Great thanks - that worked.
>> 
>> Obviously this introduces a dependency on the iostreams library, where before we only depended on the headers.  Is this going to be a problem?  Not every system has the binaries compiled for boost, although most will.  I guess I can just push this back into the repository in a new branch called gzip for now?... (starting to get the hang of this hg stuff!)
>> 
>> cheers,
>> 
>> James
>> 
>> On 11 Jul 2013, at 23:08, Andy Buckley wrote:
>> 
>>> Hi James,
>>> 
>>> Have a look at the docs here:
>>> https://github.com/tsuna/boost.m4/
>>> 
>>> I think the pre-packaged way to do it is to call BOOST_IOSTREAMS.
>>> 
>>> Feel free to update to the latest version of that boost.m4 if you like.
>>> The current version is a few months old and contains some patches by me
>>> which then got pulled into that Github repo.
>>> 
>>> Andy
>>> 
>>> 
>>> On 11/07/13 19:47, James Monk wrote:
>>>> Hi everyone,
>>>> 
>>>> I'm trying to add reading of gzipped HepMC files to Rivet (together with the event filtering, I think this would improve the io performance enough that storing events becomes worthwhile).  For this, I need to link against libboost_iostreams.[so, dylib].  There's a m4 macro in boost.m4 of 
>>>> 
>>>> 	BOOST_FIND_LIB([iostreams])
>>>> 
>>>> which you'd imagine would do the job, but seems to look for an empty filename.  There's not much documentation on that - does anyone know if/how it works?  Or an alternative neat way of finding a particular boost library?.. 
>>>> 
>>>> cheers,
>>>> 
>>>> James
>>>> 
>>>> _______________________________________________
>>>> Rivet mailing list
>>>> Rivet at projects.hepforge.org
>>>> http://www.hepforge.org/lists/listinfo/rivet
>>>> 
>>> 
>>> 
>>> -- 
>>> Dr Andy Buckley, Royal Society University Research Fellow
>>> Particle Physics Expt Group, University of Edinburgh / PH Dept, CERN
>> 
>> 
> 
> 
> -- 
> Dr Andy Buckley, Royal Society University Research Fellow
> Particle Physics Expt Group, University of Edinburgh / PH Dept, CERN