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: Building EPICS MOTOR with just a subscription to only the motorNewport module |
From: | Mark Rivers via Tech-talk <tech-talk at aps.anl.gov> |
To: | "'tech-talk at aps.anl.gov'" <tech-talk at aps.anl.gov>, Timothy Speight - STFC UKRI <timothy.speight at stfc.ac.uk> |
Date: | Tue, 7 Jun 2022 13:09:10 +0000 |
I believe I made the commits that define SUPPORT in these motor module RELEASE files:
corvette:~/devel/motor/modules>grep SUPPORT */configure/RELEASE*
motorAerotech/configure/RELEASE:SUPPORT=$(MOTOR)/..
motorNewport/configure/RELEASE:SUPPORT = $(MOTOR)/..
motorOms/configure/RELEASE:SUPPORT=$(MOTOR)/..
motorParker/configure/RELEASE:SUPPORT=$(MOTOR)/..
motorScriptMotor/configure/RELEASE:SUPPORT=$(MOTOR)/..
That was done to allow the autoconversion of adl to other OPI files. It works for a "normal" synApps distribution, because SUPPORT is then $(MOTOR)/..
Is MOTOR installed outside of SUPPORT in your installation?
I could probably fix those by moving the definition of SUPPORT to RELEASE.local and EXAMPLE_RELEASE.local.
Mark
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Timothy Speight - STFC UKRI via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, June 7, 2022 6:36 AM To: 'tech-talk at aps.anl.gov' <tech-talk at aps.anl.gov> Subject: Building EPICS MOTOR with just a subscription to only the motorNewport module Hi,
I’ve reverted to commit ‘be5dd3f’ and my module driver and EPICS motor synapps builds OK.
On the latest master for the motorNewport module for an intended complete EPICs motor build; It seems as though SUPPORT gets redefined! >> SUPPORT = $(MOTOR)/..
File in question here : https://github.com/epics-motor/motorNewport/blob/master/configure/RELEASE
I’m not sure this last commit is working so well within our build systems here at the CLF.
ERROR: Definition of SUPPORT conflicts with BUSY support.In this application a RELEASE file defines SUPPORT = /usr/local/epics/support/motor/motor-R7-2-2/..
Should I raise a PR?
Kind Regards
Tim Speight Senior Control Systems Software Engineer Central Laser Facility Science and Technology Facilities Council 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. |