EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: epics debian repository update
From: Michael Davidsaver <[email protected]>
To: Benjamin Franksen <[email protected]>, [email protected]
Date: Thu, 20 May 2010 09:09:58 -0400
On 05/19/10 15:26, Benjamin Franksen wrote:
On Mittwoch, 19. Mai 2010, Davidsaver, Michael wrote:
The difficultly is cross compiling for RTEMS. I'm not sure if it will
work out in the long term, but I have had positive feedback from the few
people who have used it.
It is great mystery to me how you could build an EPICS package at all.

The usual way, lots of trial, and lots of error :)


What about all the other cross-compiler targets and their specific
configuration?

While I've had many frustrations with it, I must say that this is were the Base build system helped me. Mostly this just worked. Of course I only cross-build RTEMS, not other host targets. There is much less chance of shared library dependency problems when you don't have shared libraries!


  I mean, how do I configure a debian package for epics base
in the first place?

Set PATH, LD_LIBRARY_PATH in the environment and patch the build system to avoid linking with -rpath.


Among the debian packaging tools is the Lintian utility which analyzes the build package for common mistakes. After ~12 years it knows about a lot of problems.

Will there be some /etc/epics.conf?

That is on hold until Andrew and I come to an agreement on how this should be implemented. Until then the EPICS_* environment variables are it.


OTOH, doesn't EPICS
need this configuration stuff at build time?

At present it actually doesn't. These are runtime parameters related to channel access and IOCs. Thankfully neither are needed during the build.



Michael



Replies:
Re: epics debian repository update Benjamin Franksen
References:
epics debian repository update Davidsaver, Michael
Re: epics debian repository update Bill Lavender
RE: epics debian repository update Davidsaver, Michael
Re: epics debian repository update Benjamin Franksen

Navigate by Date:
Prev: EPICS base compiling using Visual C++ 2010 Express Carsten Winkler (HZB)
Next: Re: epics debian repository update Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: epics debian repository update Benjamin Franksen
Next: Re: epics debian repository update Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·