Hi everyone,
I'm curious about how people manage paths in RELEASE, like EPICS_BASE,
ASYN, etc.
I've been using paths relative to the respective TOP, of this kind:
EPICS_BASE=$(TOP)/../../base
But when upgrading to 3.14.12.2 (from 3.14.11), convertRelease.pl
decided these were invalid (3 line patch attached that allows this by
canonicalising any path that exists at check time, any chance of this
please being accepted into base? )
The App Developer's Guide shows RELEASE with absolute paths
arranged under /home/epics, but surely this doesn't scale across
multiple developers or multiple working copies?
So it all made me wonder - how does everyone else do it?
- Angus
Index: base/src/tools/EPICS/Path.pm
===================================================================
--- base/src/tools/EPICS/Path.pm (revision 1268)
+++ base/src/tools/EPICS/Path.pm (revision 1269)
@@ -123,6 +123,9 @@
# Now calculate the absolute path
my $abs = File::Spec->rel2abs($path, abs_path($cwd));
+ if (-e $abs) {
+ $abs = abs_path($abs);
+ }
return LocalPath($abs);
}
- Replies:
- Re: EPICS build system, RELEASE file, and relative paths Pavel Masloff
- RE: EPICS build system, RELEASE file, and relative paths Mark Rivers
- Re: EPICS build system, RELEASE file, and relative paths Andrew Johnson
- Navigate by Date:
- Prev:
RE: Epics driver using BLT or CBLT to read FIFO wanted Mark Rivers
- Next:
Re: EPICS build system, RELEASE file, and relative paths Pavel Masloff
- 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:
quadEM R3-0 now available Mark Rivers
- Next:
Re: EPICS build system, RELEASE file, and relative paths Pavel Masloff
- 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
|