Hello Zhichu,
One of the great thing about EPICS is that there is no
fundamental difference in either the directory structures or build
files between EPICS base, an EPICS support module, an
EPICS extension or the "home" directory of an EPICS IOC.
They all have the same basic <top> directory structure
described in the Application Developer’s Guide;
A <top> directory has the following directory structure:
<top>/
Makefile
configure/
dir1/
dir2/
My suggestion is to use makeBaseApp.pl to create your
support module directory structure, Makefiles, CONFIG
files, etc., and then make modifications to suit your support
module.
Hope this helps,
Ron
Zhichu Chen wrote:
Hi,
Just curiosity, is there any manuals that I can follow? I have written a
device support and I would love to make a module version so that
maintenance would be easier for me. I can't find any clue in the
AppDevGuide, so I checked the snc/seq module and now I'm trying
to follow it.
May some of you guys explain the basic steps for me? Like is there
a makeModuleApp.pl script to create a template (I don't want to write
all those Makefile files and CONFIG files), how should I construct
the directory structure tree, how to make the application find it (I
find that I can just add "SNCSEQ=/path/to/seq" to the RELEASE
file to make the app know where to find the lib files, why? Can I
use a random name there like "MYLIB"?).
- References:
- How to write modules? Zhichu Chen
- Navigate by Date:
- Prev:
call to "assert (capacity != 0)" failed Benjamin Franksen
- Next:
Re: How to write modules? Tim Mooney
- 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:
How to write modules? Zhichu Chen
- Next:
Re: How to write modules? Tim Mooney
- 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
|