RE: Compile StreamDevice with PCRE on windows

[Freddie Akeroyd - STFC UKRI via Tech-talk <tech-talk at aps.anl.gov>]

Hi,

Do you have a 

....\EPICS\modules\PCRE\lib\windows-x64

directory containing the lib file?  EPICS will use the path  $(PCRE)/lib/$(EPICS_HOST_ARCH)  by default for items mentioned in a RELEASE file, if the lib file is in a different place then you either move it to a directory using this naming or tell EPICS to look in a different place e.g. if it is in ....\EPICS\modules\PCRE\lib then add

pcre_DIR=$(PCRE)/lib

to the stream device Makefile  

Regards,

Freddie


> -----Original Message-----
> From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Neidherr,
> Dennis Dr. via Tech-talk
> Sent: 29 April 2025 10:32
> To: tech-talk at aps.anl.gov
> Subject: Compile StreamDevice with PCRE on windows
> 
> Dear all,
> 
> I just tried to compile StreamDevice on windows with the PCRE package active.
> Without this package everything works fine. But I don't get PCRE working.
> 
> So what did I do:
> I downloaded PCRE (pre-compiled) at Sourceforge as described here
> (https://urldefense.us/v3/__https://paulscherrerinstitute.github.io/StreamD
> evice/setup.html__;!!G_uCfscf7eWS!ZfKA6yWdFPFiCYl7MTE8FME6NieocxQ
> MXHjO3TZUaz5u4e8C3576MhzCkeSlf_dEIJFVlZg4VWcZ7YjAKclB-u7s$ ).
> Then I installed the executable next to my other modules. So it looks like:
> 
> ...\EPICS\modules\asyn-R4-43
> ...\EPICS\modules\StreamDevice-2.8.26
> ....\EPICS\modules\PCRE
> 
> Then I modified my RELEASE.local file in StreamDevice and added the entry for
> PCRE (between ASYN and Base):
> PCRE=...\EPICS\modules\PCRE (I just deleted the first part of the path here for
> this text)
> 
> But when I try to compile it now, I get the following error:
> make[2]: *** No rule to make target '../../lib/windows-x64/pcre.lib', needed
> by 'stream.dll'.  Stop.
> If I interpret it correctly then he searches for the file "pcre.lib" in
> "...\EPICS\modules\StreamDevice-2.8.26\lib\windows-x64".
> But this is for sure wrong.
> 
> Do I have to add another path somewhere else before compiling?
> 
> I think I will soon switch to linux anyway, so this problem here will solve by
> itself, but nevertheless I would like to know what I am doing wrong.
> 
> Thanks and Greetings
> Dennis