EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Extensions configuration/compilation
From: David Decotigny <[email protected]>
To: [email protected]
Date: Tue, 13 Apr 2004 14:10:53 +0200

Hi,


I am new to Epics, and I do have a question that will sound stupid to you all I guess. Sorry for it in advance.

I successfully compiled epics 3.14.5 on our host (linux RH9, EPICS_HOST_ARCH set to linux-x86). And now comes the time when I try to compile some "standard" host extension prior to eventually upgrade another extension we use.

So I downloaded the extensionsConfigure tarball (20040406), unpacked it, changed the EPICS_BASE variable in extensions/configure/RELEASE to point to our epics' base.

Then I decided to compile the "caex" extension, to see how to compile a standard extension. So I downloaded it, untarred it (all is put in extensions/src/caex), and there, I can see the extensions/src/caex/Makefile contains:
TOP = ../../
include $(TOP)/config/CONFIG_EXTENSIONS
include $(TOP)/config/RULES_ARCHS


"make" of course could not find any of these inclusions. Apparently the CONFIG_EXTENSIONS file came with the "extensions" tarball, so the TOP variable seems almost right: I simply renamed "config" as "configure" in the 1st include. But the RULES_ARCH does not sit in the same directory: it might refer to <EPICS_BASE>/configure/RULES_ARCH I guess. So, in the end, the Makefile looks like:
TOP = ../../
include $(TOP)/configure/CONFIG_EXTENSIONS
MY_EPICS=/home/ddecotig/download/src/epics-base-3.14.5
include $(MY_EPICS)/configure/RULES_ARCHS


And, obviously this is not completely correct, for a "make" will be infinitely recursive:
[...]
make[434]: Entre dans le répertoire `/tmp/epics/extensions/src/caex/O.linux-x86/O.linux-x86'
make -f ../Makefile TOP=../..//.. T_A=linux-x86 install
make[435]: Entre dans le répertoire `/tmp/epics/extensions/src/caex/O.linux-x86/O.linux-x86'
make -f ../Makefile TOP=../..//.. T_A=linux-x86 install
make[436]: Entre dans le répertoire `/tmp/epics/extensions/src/caex/O.linux-x86/O.linux-x86'
[...]


I then noticed another RULES_ARCH file in <EPICS_BASE>/config/ directory, and, if I choose that one instead of the one in <EPICS_BASE>/configure/, I get:
[pollindd] epics/extensions/src/caex >make
make: *** No rule to make target `install.linux-x86', needed by `install.cross'. Stop.
zsh: exit 2 make


So I'm sure I missed something, but what ? Perhaps I did not look at the right documentation ? Could someone tell what are the recommended steps to configure/compile an extension ? Would you advise to choose another simple extension to get used to the extensions configuration/compilation process ?

Sorry for this. Thanks a lot in avance,

--
David Decotigny -- LLR/info -- Bureau 04 1012D -- poste 4404


Replies:
Re: Extensions configuration/compilation David Decotigny

Navigate by Date:
Prev: RE: Bidirectional device support Ernest L. Williams Jr.
Next: Re: Extensions configuration/compilation David Decotigny
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Bidirectional device support Luedeke Andreas
Next: Re: Extensions configuration/compilation David Decotigny
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  <20042005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·