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: How to use INSTALL_LOCATION with system directories |
From: | Lucas Russo via Tech-talk <tech-talk at aps.anl.gov> |
To: | Maren Purves <m.purves at eaobservatory.org> |
Cc: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
Date: | Tue, 10 Oct 2023 09:07:47 +0200 |
The part I don't understand is why you want to install it in system space in the first place.We never have. Install it somewhere you have write access to and add that to your $PATH?Maren PurvesHead of Instrument and Telescope SoftwareEast Asian Observatory/JCMTOn Mon, Oct 9, 2023 at 5:28 AM Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> wrote:On Mon, 9 Oct 2023 at 17:03, Jure Varlec via Tech-talk <tech-talk at aps.anl.gov> wrote:On 10/9/23 16:15, Lucas Russo via Tech-talk wrote:
Caution: This email originated from outside of Cosylab.
Hi Ralph, Abdalla,
I understand. Because there's no separate "installation phase" itdoesn't seem possible to achieve what I was thinking.
Thanks,
LucasHi Lucas,
Why not? Unless I misunderstood what you want, you could do
make INSTALL_LOCATION=${HOME}/tmp/staging/ FINAL_LOCATION=/opt/test
sudo mv ${HOME}/tmp/staging/ /opt/test
sudo chown -R epics:epics /opt/test # Or root, or whateverPerhaps having the staging directory under $(TOP) or /tmp makes more sense, it depends on your case, but you get the idea. Would this work for you?
Or, if you really want to use make, you can obviously use INSTALL_LOCATION for your staging area, FINAL_LOCATION for the target area and add something likefinal-install:
mkdir -p $(FINAL_LOCATION); cp -a $(INSTALL_LOCATION)/* $(FINAL_LOCATION)to the end of your top Makefile.Cheers,
~Ralph