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: [makefile] adding a library to an EPICS application |
From: | Pavel Maslov <[email protected]> |
To: | Martin Konrad <[email protected]> |
Cc: | EPICS Tech Talk <[email protected]> |
Date: | Thu, 20 Dec 2012 13:37:19 +0400 |
Hi,
> In general I recommend making use of the EPICS build system if youOf course Andrew is right. Someone has to spend some time to write the
> can because we take care of things like creating dependency files and
> handling multiple architecture builds from the same source tree; most
> other build systems need you to do extra work for that kind of
> thing.
EPICS specific rules. But in case of CMake most of this work has been
done already (see the links in my first mail).
Building for multiple architectures comes for free with CMake as it
supports out-of-source builds (actually they are default).
Cross-building is possible as well. It's supported with many different
tool chains. Of course you can add your own tool chain as well.
Creating dependency files should be an easy exercise but I think you
don't need them with CMake (it takes care of things like that
automatically). With Make it's difficult to write build rules that work
for parallel builds (e.g. make -j 4) with CMake it's difficult to write
rules that do not.
So I would still recommend using CMake for apps/libs that build on top
of EPICS base.
Regards,
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