Hi,
I'm using Michaels packages, too.
> Our build system wasn't designed with the needs of distro
> packaging in mind, but we are slowly moving in the direction of making
> that possible.
CMake provides a very clean way to cross-build as well as package for different
platforms (mainly because you get out-of-tree builds for free). That's why
there already has been some discussion about CMake last year. Michael
published his CMake files for building base here:
https://code.launchpad.net/~mdavidsaver/epics-base/cmake
I am using CMake to build a device support (because it uses several libraries
that are much easier to find and use from CMake). I'm still using the
traditional Makefile approach for my IOC.
In the last weeks support for packaging CMake components into different deb/rpm
files was added to CPack. This means that you can now easily create several
deb/rpm files from one source tree (e.g. one for each of applications,
libraries, and headers). It is even possible to derive the dependencies
between deb packages from the dependencies between the components
automatically. Support for this is coming with CMake 2.8.5 which will be
released next week.
Cheers
Martin
--
Dipl. Phys. Martin Konrad
Technische Universität Darmstadt
Institut für Kernphysik
Schlossgartenstr. 9
64289 Darmstadt
Tel: +49-6151-16-5121
Fax: +49-6151-16-4321
- References:
- status of Debian/Ubuntu packages/repositories Jameson Graef Rollins
- Navigate by Date:
- Prev:
RE: PyEpics and Python threads Vigder, Mark
- Next:
Re: PyEpics and Python threads Matt Newville
- 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:
Re: status of Debian/Ubuntu packages/repositories Bill Lavender
- Next:
PyEpics and Python threads Vigder, Mark
- 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
|