As I understand it, the PCRE library is used if your protocol file uses
regular expression for parsing input:
getRegexTitle {
out "REGEX_TITLE";
in "%.1/<title>(.*)<\/title>/"
}
So, if your protocol files don't use this feature, you should be fine.
This is documented here:
-
https://github.com/paulscherrerinstitute/StreamDevice/blob/e6b2944c/streamApp/regexp.README
- https://paulscherrerinstitute.github.io/StreamDevice/setup.html
Cheers
--
Rémi NICOLE <remi.nicole at cea.fr>
CEA/DRF/IRFU/DIS/LDISC
On Wed, 2023-03-22 at 22:12 +0000, Marco A. Barra Montevechi Filho via
Tech-talk wrote:
> Hello all, i have an areaDetector IOC which im cross-compiling for
> aarch64. The ioc also uses streamDevice 2.8.22 and is being compiled
> in an ubuntu 16.04 container.
>
> I have another ubuntu 16.04 old container in which i compiled it in
> the past, but he configuration of the container is kinda messy and im
> improving things.
>
> I remember i did something ugly in the old container and it has lpcre
> somewhere, but i couldnt find it, although i can recompile the ioc in
> it. I also couldnt solve the compilation issue in the new container
> withapt install libpcre3 libpcre3-dev or anything similar.
>
> So in the new container i just found PROD_SYS_LIBS_DEFAULT += pcre in
> a makefile, commented it and it compiled nicely.
>
> I understand its a lib for regex in perl and streamDevice might use
> it but might already have it out-of-the-box.
>
> My question is: am i breaking my IOC in ways im going to regret? Or
> just getting rid of old dependencies that are not needed anymore?
>
> Thanks for any help,
>
> Marco
>
> Aviso Legal: Esta mensagem e seus anexos podem conter informações
> confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo
> e considere eventual consulta ao remetente antes de copiá-la,
> divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano,
> por favor avise o remetente e apague-a imediatamente.
> Disclaimer: This email and its attachments may contain confidential
> and/or privileged information. Observe its content carefully and
> consider possible querying to the sender before copying, disclosing
> or distributing it. If you have received this email by mistake,
> please notify the sender and delete it immediately.
- Replies:
- Re: Doubts about libpcre in compilation Marco A. Barra Montevechi Filho via Tech-talk
- References:
- Doubts about libpcre in compilation Marco A. Barra Montevechi Filho via Tech-talk
- Navigate by Date:
- Prev:
回覆: Value of Renishaw absolute encoder exceeds its maximum Chiang, Liang-Chih [江良志] via Tech-talk
- Next:
Job Opportunity BESSY II Smith, William via Tech-talk
- 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:
Doubts about libpcre in compilation Marco A. Barra Montevechi Filho via Tech-talk
- Next:
Re: Doubts about libpcre in compilation Marco A. Barra Montevechi Filho via Tech-talk
- 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
|