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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: EPICS Soft IOC question |
From: | Bruce Hill <[email protected]> |
To: | Andrew Cox <[email protected]>, <[email protected]> |
Date: | Thu, 1 Sep 2011 14:09:29 -0700 |
Hi Andrew, One thing that tends to be different for an EPICS software site is that each IOC typically has it's own release cycle. Any organization or top down makefile support for your IOC's is purely for your benefit. Thus, there are probably nearly as many ways of organizing them as there are EPICS sites. The other point to consider is whether or not you intend to make your own updates or additions to the EPICS base or any of the available EPICS modules. To build your IOC, you need have a directory structure that organizes the various versions of base and modules that your IOC needs. If you're also going to make your own versions of base and/or modules, you'll want those in version control as well. Here's the way my group organizes them, FWIW. $(RELEASES)/epics/base/<version> $(RELEASES)/epics/modules/<module_name>/<version> $(RELEASES)/epics/ioc/<hutch>/<ioc_name>/<version> $(RELEASES)/epics/screens/edm/<hutch>/<version> In svn, it looks like this: ~/svn_wa/epics/base/current ~/svn_wa/epics/modules/<module_name>/current ~/svn_wa/epics/ioc/<hutch>/<ioc_name>/current ~/svn_wa/epics/screens/edm/<hutch>/current HTH, - Bruce On 09/01/2011 08:45 AM, [email protected] wrote: Try this... and see what comes out! ${EPICS_BASE}/bin/${EPICS_HOST_ARCH}/makeBaseApp.pl -t example base ${EPICS_BASE}/bin/${EPICS_HOST_ARCH}/makeBaseApp.pl -i -t example -a ${TARGET_ARCH} base I have my own directory structure in my SVN tree. I built my own makefiles. No sure you want to do that for only a few IOCs. The directory structure I have is as follow .../svn/<synchrotronId>/drivers/<driverName>/{db|doc|medm|qt|msi|iocBoot|dbd|medm|stream|src|...}/ .../svn/<synchrotronId>/iocs/<iocName>/{db|doc|medm|iocBoot|dbd|msi|medm|qt|src|...}/ .../svn/<synchrotronId>/opis/<opiSoftware>/{bin|etc|...}/ The Makefiles build, configure, and install the software based on hostname, arch, etc... So yes, you can make it as complicated as you want ;-) Good luck, -- E On 16:02 Wed 31 Aug , Andrew Cox wrote:Hi, I have downloaded the EPICS IOC core on a redhat machine. I need to run atleast 3-4 soft IOc on this machine, but i am not able to decide on the directory structure. i do not want it to be complicated. Can anyone help me with a directory structure for the database, drivers etc ? Thanks, Andrew -- Bruce Hill Member Technical Staff SLAC National Accelerator Lab 2575 Sand Hill Road M/S 10 Menlo Park, CA 94025 |