Hi,
If an extension has a Makefile.Host and a Makefile that includes files
from $(TOP)/config it is a R3.13 type extension and you should use the
extensions/config tarfile files. Set EPICS_BASE in the RELEASE file
to your R3.14.5 base. R3.13 type extensions can be built with R3.14 base.
You can have both extensions/configure and extensions/config in the same
extensions top directory. The R3.13 type extensions will use the config
files and extensions that have been converted to R3.14 Makefiles will
use the configure directory files.
Janet
David Decotigny wrote:
Hi,
Sorry for the previous post again, I did not look at the right doc.
I post the way I made caex compile here, I hope it is the "right" way:
- cd anywhere
- "<EPICS_BASE>/bin/linux-x86/makeBasext.pl -b <EPICS_BASE>" to
generate a template
- untar caex in the src/ directory
- rename src/caex/Makefile.Host as Makefile, and customize the 2
includes (inspired from the simpleExt and exampleExt templates):
include $(TOP)/configure/CONFIG
[...]
include $(TOP)/configure/RULES
- update the DIRS variable in src/Makefile
Is it the general way to do the things correctly ?
BTW, http://ics-web1.sns.ornl.gov/edm/ seems to be down right now.
Sincerely,
- References:
- Extensions configuration/compilation David Decotigny
- Re: Extensions configuration/compilation David Decotigny
- Navigate by Date:
- Prev:
RE: Bidirectional device support Liyu, Andrei
- Next:
RE: Bidirectional device support Thompson, David H.
- 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: Extensions configuration/compilation Robert Soliday
- Next:
MVME5110 Dirk Zimoch
- 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
|