On 4/17/21 4:54 PM, Freddie Akeroyd - STFC UKRI wrote:
Hi Marty,
Do you also build your programs linked statically on linux too? If not, it might be worth doing that too - I believe any purely link order issues you may see with travis windows should also occur when linking statically on linux
Regards,
Freddie
How do I do this on Linux?
I also have a couple of questions about the travis builds.
1) Why are there two sets of builds,
2) Do any of the gcc or clang builds statically linked.
Marty
-----Original Message-----
From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Mark Rivers via
Tech-talk
Sent: 17 April 2021 13:37
To: Marty Kraimer <mrkraimer at comcast.net>
Cc: EPICS Tech-Talk <tech-talk at aps.anl.gov>
Subject: Re: WIN_32
Hi Marty,
You are making progress, the error is now different:
/home/travis/.source/pvaClient/lib/linux-x86_64/libpvaClient.a(pvaClient.o): In
function `epics::pvaClient::PvaClient::~PvaClient()':
/home/travis/.source/pvaClient/src/O.linux-x86_64/../pvaClient.cpp:156:
undefined reference to `epics::pvAccess::ClientFactory::stop()'
So now a function in pvaClient is not finding the pvAccess functions. That is
probably a link order problem.
Try this:
EPICS_BASE_PVA_CORE_LIBS = pvaClient pvDatabase pvAccess pvAccessCA
pvData Com
Or leave EPICS_BASE_PVA_CORE_LIBS as it was originally and add pvaClient
here:
PROD_HOST += serviceMain
serviceMain_SRCS += serviceMain.cpp
serviceMain_LIBS += controlRecord
serviceMain_LIBS += powerSupplyRecord
serviceMain_LIBS += linkRecord
serviceMain_LIBS += pvaClient
serviceMain_LIBS += $(EPICS_BASE_PVA_CORE_LIBS)
Mark
________________________________
From: Marty Kraimer <mrkraimer at comcast.net>
Sent: Saturday, April 17, 2021 7:07 AM
To: Mark Rivers
Cc: EPICS Tech-Talk
Subject: Re: WIN_32
On 4/16/21 5:44 PM, Mark Rivers wrote:
EPICS_BASE_PVA_CORE_LIBS = pvDatabase pvAccess pvAccessCA pvData
pvaClient Com
Mark,
I made that change.
The pull request still fails for windows and rtems.
Does it build for You on windows?
Marty
This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.
- Replies:
- RE: WIN_32 Freddie Akeroyd - STFC UKRI via Tech-talk
- References:
- WIN_32 Marty Kraimer via Tech-talk
- RE: WIN_32 Mark Rivers via Tech-talk
- Re: WIN_32 Marty Kraimer via Tech-talk
- RE: WIN_32 Mark Rivers via Tech-talk
- Re: WIN_32 Marty Kraimer via Tech-talk
- Re: WIN_32 Mark Rivers via Tech-talk
- Navigate by Date:
- Prev:
Re: PVA crossing network segments Michael Davidsaver via Tech-talk
- Next:
RE: WIN_32 Freddie Akeroyd - STFC UKRI 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:
Re: WIN_32 Mark Rivers via Tech-talk
- Next:
RE: WIN_32 Freddie Akeroyd - STFC UKRI 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
|