| 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 | 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: mrkSoftTest doesn't compile |
| From: | Andrew Johnson <[email protected]> |
| To: | Ralph Lange <[email protected]> |
| Cc: | Janet Anderson <[email protected]>, EPICS Core Talk <[email protected]> |
| Date: | Thu, 17 Nov 2005 09:17:56 -0600 |
Hi Ralph, Ralph Lange wrote:
Is it illegal to use two compiled-in paths? From first glance I wouldn't see why. Does the build system rely on just one path being defined? If so: Is that limitation justified?
There is no problem having more than one path defined (it will just look through them one after the other until it finds the .so file), but you must ensure that it will never find a different version of the libraries at runtime than it saw at compile time, as I think I wrote yesterday - your 'final install' path should be pointing to an empty or non-existent directory until that version of base has been installed. You might also want to adjust the search order so it looks in the local build first by changing the order of the items in your mrkSoftTest's configure/RELEASE file; shared library searches should occur in the same order as the lines in that file.
- Andrew -- * * Matt Santos / / Leo McGarry * * For a Brighter America * *