Hi Geoff,
Here is an example from one of my application Makefiles:
# <name>_registerRecordDeviceDriver.cpp will be created from <name>.dbd
CARSApp_SRCS_DEFAULT += CARS_registerRecordDeviceDriver.cpp
CARSApp_SRCS_vxWorks += CARSVX_registerRecordDeviceDriver.cpp
CARSApp_SRCS_Linux += CARSLinux_registerRecordDeviceDriver.cpp
.....
Here is CARSInclude.dbd
corvette> more CARSInclude.dbd
include "CARSCommonInclude.dbd"
Here is CARSVXInclude.dbd
corvette> more CARSVXInclude.dbd
include "CARSCommonInclude.dbd"
include "mcaCanberraSupport.dbd"
.....
include "quadEMSupport.dbd"
include "vxStats.dbd"
Here is CARSLinuxInclude.dbd
corvette> more CARSLinuxInclude.dbd
include "CARSCommonInclude.dbd"
include "mcaCanberraSupport.dbd"
include "dxpSupport.dbd"
Here is CARSCommonInclude.dbd
corvette> more CARSCommonInclude.dbd
include "base.dbd"
include "asyn.dbd"
include "drvAsynSerialPort.dbd"
.....
include "roperCCDSupport.dbd"
Note that this gets really ugly as the number of architecture-specific
...dbd files increases. I have talked to the EPICS developers here (Marty
Kraimer, Andrew Johnson, and others) and I think we came to the
concensus that .dbd files should be put in architecture-specific
directories, just like object files are.
Mark Rivers
- Navigate by Date:
- Prev:
Re: dbd files for different OS Geoff Savage
- Next:
compiler base using C++ Builder 6 Ding Jianguo
- 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:
Re: dbd files for different OS Geoff Savage
- Next:
compiler base using C++ Builder 6 Ding Jianguo
- 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
|