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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Pointing an IOC to system-level lib files for build |
From: | Katie Matusik via Tech-talk <tech-talk at aps.anl.gov> |
To: | Mark Rivers <rivers at cars.uchicago.edu> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Wed, 28 Apr 2021 13:11:48 -0700 |
Hi Katie,
In your IOC application Makefile add lines like these:
myExternalLib_DIR = /home/me/myExternalPackage
PROD_LIBS += myExternalLib
Where /home/me/myExternalPackage is the directory containing myExternalLib.so.
Mark
________________________________
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Katie Matusik via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, April 27, 2021 11:40 AM
To: tech-talk
Subject: Pointing an IOC to system-level lib files for build
Hi everyone,
I have a .so file that lives on the system and is required by an IOC for successful compilation. A workaround at the moment is to build the IOC, let it fail so that it creates the ../../lib/linux-x86_64 directory, then manually symlink the files from the system directory to this lib directory so that they exist in the subsequent build attempt. Could someone let me know what is the correct way to circumvent this so that the IOC will include the system directory during its first build?
Thanks so much and please let me know if you need further information.
Best,
Katie
--
Katie Matusik
Systems Engineer
Sigray, Inc.<http://www.sigray.com/>
5750 Imhoff Drive, Suite I
Concord, CA 94520 USA
Office: 1 (925) 326 - 7926
[https://static1.squarespace.com/static/56de1f4a2fe1318cf0aacc98/t/5d9e0fa57996446a078a8e1a/1570639781104/Logo_gmail_small.png?format=300w]
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited