Hello,
I have run into a problem when building the V4 pvCommonCPP module into an IOC that also makes use of boost libraries.
My setup is
Red Hat Enterprise Linux Workstation release 6.7 (Santiago)
pvCommonCPP version 4-0-2 (looking at README suggests boost version 1-53-0)
external boost installation version 1-48-0
Specifically I'm compiling ADCore 2-4 with V4 plugin/driver (V4 dependency) enabled and pluginTest unit tests (external boost dependency) enabled.
I cannot compile my application because the boost header files inside pvCommonCPP are found and are not compatible, and so I have the following questions...
1) Is pvCommonCPP required when compiling against V4 modules? The V4 documentation has
"In addition for C++ there is the utility module pvCommonCPP. This contains boost, needed in particular for shared_pointers, and a microbenchmark framework. If you don't intend to use the latter then you may not need pvCommonCPP, depending on your compilers support for shared_pointers."
which suggests I wouldn't need it? However, other V4 modules have been released against this version of the pvCommonCPP module and so the reference exists if I include any V4 modules.
2) Should the other V4 modules have been released against this pvCommonCPP module in my case, or could they have been released without the reference as I have shared pointers available anyway?
3) If pvCommonCPP is required is there a way to specify which version of boost it can be compiled against?
4) If using pvCommonCPP along with it's version of boost, does the whole set of boost libraries get built and installed?
Thanks, Alan
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- Replies:
- Re: Using V4 pvCommonCPP module with external boost library Andrew Johnson
- RE: Using V4 pvCommonCPP module with external boost library david.hickin
- Navigate by Date:
- Prev:
msi for windows IOC build ronaldo.mercado
- Next:
Re: msi for windows IOC build Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: msi for windows IOC build Andrew Johnson
- Next:
Re: Using V4 pvCommonCPP module with external boost library Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|