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 | 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: EpicsHostArch on mingw64 |
From: | Freddie Akeroyd - STFC UKRI via Core-talk <core-talk at aps.anl.gov> |
To: | "ralph.lange at gmx.de" <ralph.lange at gmx.de>, EPICS Core Talk <core-talk at aps.anl.gov> |
Date: | Sun, 9 Jun 2024 15:44:14 +0000 |
Hi Ralph, Thank you for the link to the discussion – very interesting. There seem to be potential pitfalls to any approach so I think improving the error message is the best thing to do for
now – I’ve created a PR https://github.com/epics-base/epics-base/pull/492 Regards, Freddie From: Ralph Lange <ralph.lange at gmx.de>
----BEGIN PGP MESSAGE---- See https://bugs.launchpad.net/epics-base/+bug/1873406 and the lengthy discussion that is documented there. Improving the error message sounds good, as it is indeed safe and probably doesn't hurt anyone's feelings. Running gcc sounds clever, but it could also hit the "don't depend on user environment setting" criteria. Which compiler is used depends on the architecture setting. Calling the one in the PATH to find the architecture would be biased. On the other hand: If the user has multiple compiler chains installed, no script will be able to read their mind finding out which one they would like to use. Cheers, ----END PGP MESSAGE---- |