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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Including libraries in subroutines |
From: | Stephen Molloy <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Tue, 28 Jun 2016 18:42:50 +0000 |
Hi,
I just wanted to confirm that Andrew’s recommendation to use PROD_SYS_LIBS in the appropriate Makefile did the trick.
Many thanks for the very fast response.
Steve
From: Stephen Molloy <[email protected]>
Date: Tuesday 28 June 2016 at 00:27 To: "[email protected]" <[email protected]> Subject: Re: Including libraries in subroutines Thanks Andrew.
libwiringPi.so can be found in /usr/lib on my system, so I will try your suggested PROD_SYS_LIBS solution.
(But tomorrow — it’s late in Sweden now…)
Steve
From: Stephen Molloy <[email protected]>
Date: Monday 27 June 2016 at 23:53 To: "[email protected]" <[email protected]> Subject: Including libraries in subroutines
Hi,
Let me apologise in advance for a very basic question.
I have some C code that I would like to convert to a subroutine record. I normally build the executable with g++ using a -lwiringPi
flag, but I don’t know the correct way to do this in order to compile the EPICS subroutine. Is there a standard place I should put the library, or is there some change I need to make to the Makefile (and, if so, which Makefile?)
to get this to work?
Steve
|