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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Multiple OS Build |
From: | Mark Rivers <[email protected]> |
To: | "'Hugo Slepicka'" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Mon, 9 Jan 2017 17:44:31 +0000 |
Hi Hugo, I have done this by just using a few new files and soft links in base/configure/os. So in addition to linux-x86 and linux-x86_64 I am building for 3 additional Linux architectures which I call linux-x86_64-gcc42, linux-x86-gcc43, and linux-x86_64-rhel6 lrwxrwxrwx 1 epics epics 26 Dec 9 2015 CONFIG.Common.linux-x86_64-rhel6 -> CONFIG.Common.linux-x86_64 lrwxrwxrwx 1 epics epics 26 Dec 9 2015 CONFIG.linux-x86_64-rhel6.Common -> CONFIG.linux-x86_64.Common lrwxrwxrwx 1 epics epics 32 Dec 9 2015 CONFIG.linux-x86_64-rhel6.linux-x86_64-rhel6 -> CONFIG.linux-x86_64.linux-x86_64 lrwxrwxrwx 1 epics epics 23 May 7 2015 CONFIG.Common.linux-x86-gcc43 -> CONFIG.Common.linux-x86 lrwxrwxrwx 1 epics epics 26 May 6 2015 CONFIG.Common.linux-x86_64-gcc42 -> CONFIG.Common.linux-x86_64 lrwxrwxrwx 1 epics epics 23 May 7 2015 CONFIG.linux-x86-gcc43.Common -> CONFIG.linux-x86.Common lrwxrwxrwx 1 epics epics 26 May 7 2015 CONFIG.linux-x86-gcc43.linux-x86-gcc43 -> CONFIG.linux-x86.linux-x86 lrwxrwxrwx 1 epics epics 26 May 6 2015 CONFIG.linux-x86_64-gcc42.Common -> CONFIG.linux-x86_64.Common lrwxrwxrwx 1 epics epics 32 May 6 2015 CONFIG.linux-x86_64-gcc42.linux-x86_64-gcc42 -> CONFIG.linux-x86_64.linux-x86_64 -rw-r--r-- 1 epics epics 1828 May 7 2015 CONFIG_SITE.Common.linux-x86-gcc43 -rw-r--r-- 1 epics epics 1833 May 6 2015 CONFIG_SITE.Common.linux-x86_64-gcc42 For files which need to be different from the distribution files I create new files, while for those that just need a different name I use soft links. In my case those additional architectures are on different computers that all share the same file system. I just change the login files on those computers to define EPICS_HOST_ARCH
as appropriate. Mark From: [email protected] [mailto:[email protected]]
On Behalf Of Hugo Slepicka Hi All, I would like some input from the community regarding the organization of EPICS build for multiple OS targets (not cross-compiling), e.g. RHEL (5, 6, 7), Debian and other flavors available to coexist in a shared directory structure. How is the community handling cases similar to rhel7-x86_64 versus rhel6-x86_64 given that "EPICS_HOST_ARCH" returns "linux-x86_64" for both? One possible solutions would be to use something like: <shared_path>/<os_version>/base/.../<EPICS_HOST_ARCH>/... - where os_version would be: rhel5, rhel6, deb7, deb8, etc.
Thanks, Hugo |