I've occasionally run into weirdness when I have a PROD linking against a LIBRARY built in the same directory. Is there some reason that the build directory isn't included in the linker search path? That is "-L." in addition to "-L$(TOP)/lib/$(T_A)".
In this case I discovered that the mingw cross compiler now includes libevr.a, as does mrfioc2... At least in this case the order of the rules tries to link the executable before the locally built library is installed $(TOP)/lib, so the linker finds the system library. I'd imagine that in other situations this could result in linking against an older version of a library.
- Replies:
- Re: linker search path (why not -L. ?) Johnson, Andrew N.
- Navigate by Date:
- Prev:
Re: Fwd: Re: CSS shows "Disconnected" for all PV's with Base 3.15.2 (?) Torsten Bögershausen
- Next:
Re: linker search path (why not -L. ?) Johnson, Andrew N.
- Index:
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:
Jenkins build is back to normal : epics-base-3.15-win32-test #13 APS Jenkins
- Next:
Re: linker search path (why not -L. ?) Johnson, Andrew N.
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·