Hi Andrew,
> I'm wondering if we should change the way we build the PV Gateway to
> make it a stand-alone module instead of depending on extensionsConfig.
As you know, I'm not a friend of the old build system, mainly since
1. even in the most simple cases you have to customize files like
configure/RELEASE.
2. it does not support "real" out-of-tree builds
3. it includes files outside the $(TOP) directory without finding them
automatically. Renaming an upstream directory of some other EPICS
component might break your build.
That's why I suggested building the gateway with CMake a while ago [1].
Building the gateway with CMake removes all dependencies on the
extensions directory. Unfortunately my patch never made it into the repo
[2]. I pushed the patch to [3] to ease review. Note that it is using
Michael's CMake files so he deserves the most of the credit.
Let me know what you think.
Cheers,
Martin
P.S.: We might want to remove the Debian packaging stuff in favor of the
existing more Debian-style way of building cagateway [4]. This was
intended to be a
[1] http://www.aps.anl.gov/epics/tech-talk/2011/msg01717.php
[2] http://www.aps.anl.gov/epics/tech-talk/2011/msg01884.php
[3] https://code.launchpad.net/~info-martin-konrad/epics-gateway/cmake
[4] https://github.com/epicsdeb/epics-cagateway
--
Martin Konrad
Control System Engineer
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: [email protected]
- Navigate by Date:
- Prev:
Re: putlog patch for gateway Konrad, Martin
- Next:
Building RTEMS cross tools Benjamin Franksen
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
- Navigate by Thread:
- Prev:
Re: putlog patch for gateway Konrad, Martin
- Next:
Building RTEMS cross tools Benjamin Franksen
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
|