Hi Geoff,
I guess you are looking for "Specifying libraries to be linked when
creating the product", which is the title of section 4.6.19.4 in the
Application Developer's Guide. ;-)
Nevertheless - the following two definitions should do the job:
<prodname>_LIBS += <library-name>
Libraries to be used for linking the named product.
<library-name>_DIR = <path-to-that-library>
Location of external library (if not system library or in BASE).
For libraries from a <module> mentioned in the RELEASE file you
should use <module>_LIB to specify the location.
Hope this helps,
Ralph
>>>>> "Geoff" == Geoff Savage <[email protected]> writes:
> Hi,
> To include the python library in a build of a support module I added
> camodule_LDFLAGS and camodule_SYS_PRODS to my Makefile. Are these the
> most appropriate definitions to use? When I used USR_LIBS and PROD_LIBS
> it tried to find a rule to build the specified libraries. Of course no
> rule exists since the library is prebuilt.
> Thanks for any advice.
> Geoff
- References:
- including external libraries in EPICS R3.14.2 builds Geoff Savage
- Navigate by Date:
- Prev:
Re: EPICS collaboration meeting presentations Till Straumann
- Next:
Re: R3.14 and registerRecordDeviceDriver Kate Feng
- 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:
including external libraries in EPICS R3.14.2 builds Geoff Savage
- Next:
Serial I/O for Linux Eric Williams
- 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
|