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: Lowest compatible version of asyn for base 3-15.9 |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | Timothy Speight - STFC UKRI <timothy.speight at stfc.ac.uk> |
Cc: | tech-talk <tech-talk at aps.anl.gov> |
Date: | Tue, 12 Jul 2022 16:51:15 +0000 |
Hi Tim, The lastest versions of asyn should still work fine with older versions of base. I have tried to maintain backwards compatibility with old versions of base. This is discussed
in the release notes for versions R4-37 and R4-38. https://epics-modules.github.io/master/asyn/R4-42/RELEASE_NOTES.html I just tested that the latest master branch of asyn builds fine with base 3.15.5.
Are you having problems building or using the latest version of asyn with base 3.15? Mark From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of
Timothy Speight - STFC UKRI via Tech-talk Hi, Is there a suggested version of asyn I can use if I’m not using base 7 but the latest base 3.15? I see in the latest releases that a lot of the overloads for are using richer type ints that are only served by base 7. e.g. FtypeUINT64 https://epics.anl.gov/base/R3-15/9-docs/menuFtype.html vs
https://epics.anl.gov/base/R7-0/6-docs/menuFtype.html Kind Regards Tim Speight This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and
should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry
out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. |