Note that the new motor directory structure, which is similar to base 7 with a modules directory, has the same problem. I have to manually delete the modules/RELEASE* files when changing the version of base, asyn etc.
It does not seem to me that this is how the build system should work.
Mark
Sent from my iPhone
On Nov 2, 2019, at 8:10 AM, Mark Rivers <[email protected]<mailto:[email protected]>> wrote:
I just updated my base-7.0.3 to base-7.0.3.1 by doing the following:
git pull
git checkout R7.0.3.1
git submodule update
Renamed the directory from base-7.0.3 to base-7.0.3.1.
make realclean realuninstall
This fails because the modules/RELEASE*.local files still refer to the old directory base-7.0.3. I had to delete those files manually.
I find this frustrating. Is there a reason that those files cannot be removed with realclean or realuninstall?
Mark
- References:
- Base 7 modules/RELEASE*.local files Mark Rivers via Core-talk
- Navigate by Date:
- Prev:
Re: Architecture dependent dbd files Jeong Han Lee via Core-talk
- Next:
Re: Base 7 modules/RELEASE*.local files Johnson, Andrew N. via Core-talk
- Index:
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:
Base 7 modules/RELEASE*.local files Mark Rivers via Core-talk
- Next:
Re: Base 7 modules/RELEASE*.local files Johnson, Andrew N. via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
<2019>
2020
2021
2022
2023
2024
|