[...]
I am sure you two are aware of the difference, but people not so
familiar with GNU make intricacies may be confused.
Absolutely right. No reason to talk gibberish. Have a look at Base's PR#70 - Andrew separated out things very nicely. I am getting some progress on a Google Test for EPICS integration which now easily fits itself into the testing targets of the EPICS build system. My original double-colon approach was minimally invasive but clearly not the best way to handle this. NB. Ran into a minor bug in make (4.2.1): if you're defining multiple grouped target rules (that use the '&:' separator), make creates bogus warnings about "overriding recipe for target '&'" - the rules work fine, though. Cheers, ~Ralph
- Replies:
- Re: tapfiles double-colon rule Johnson, Andrew N. via Core-talk
- References:
- tapfiles double-colon rule Johnson, Andrew N. via Core-talk
- Re: tapfiles double-colon rule Ralph Lange via Core-talk
- Re: tapfiles double-colon rule Johnson, Andrew N. via Core-talk
- Re: tapfiles double-colon rule Ben Franksen via Core-talk
- Navigate by Date:
- Prev:
Re: [Merge] ~dirk.zimoch/epics-base:dbChannelForDBLinks into epics-base:7.0 Dirk Zimoch via Core-talk
- Next:
Build failed: epics-base base-appveyor-17 AppVeyor 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:
Re: tapfiles double-colon rule Ben Franksen via Core-talk
- Next:
Re: tapfiles double-colon rule 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
|