EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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  <20222023  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  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Issue with RULES_BUILD of seq 2.2.9
From: Han Lee via Tech-talk <tech-talk at aps.anl.gov>
To: NICOLE Remi <remi.nicole at cea.fr>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 11 Aug 2022 09:15:47 -0700

Hi,

Once you use INSTALL_LOCATION for any other packages, you will not get the source code in that location. You only see header files, compiled libs, and so on.
What you only need is to execute

echo "INSTALL_LOCATION:=$(INSTALL_LOCATION_SNCSEQ)" > configure/CONFIG_SITE.local

If you want to keep source codes, you can add several workflows in your internal build tool to copy all source codes into that location.

Best,
Han


On Thu, Aug 11, 2022 at 6:24 AM NICOLE Remi via Tech-talk <tech-talk at aps.anl.gov> wrote:
Hello all!

I recently tried to upgrade our seq package in our internal build tool
from seq 2.2.6 to seq 2.2.9, and came across an issue.

If I understood correctly, the 2.2.9 version introduces a more modern
RULES_SNCSEQ, which gets installed through CFG, and the old RULES_BUILD
sources the new RULES_SNCSEQ for backwards compatibility.

The way that I'm building it, is by using INSTALL_LOCATION to install
seq in a separate directory, and then drop the original source code.

The issue that I have is that RULES_BUILD and RULES_SNCSEQ are both in
configure/ in the source code, but in the target directory, RULES_BUILD
gets installed in the target configure/, but RULES_SNCSEQ gets
installed under cfg/.

The way RULES_BUILD tries to include RULES_SNCSEQ is by including in
the same directory, which is not the case when using INSTALL_LOCATION.

My current ugly workaround is to have this in RULES_BUILD:

-include $(dir $(lastword $(MAKEFILE_LIST)))/RULES_SNCSEQ
-include $(TOP)/cfg/RULES_SNCSEQ

Which is not optimal since it will silently do nothing if no file is
found.

If I try to always include it from cfg/, the build of seq fails to find
the file, as it does not get installed early enough.

Is it possible to place RULES_SNCSEQ directly under cfg/ in the
upstream source?

Kind regards
--
Rémi NICOLE <remi.nicole at cea.fr>
CEA/DRF/IRFU/DIS/LDISC


--
Jeong Han Lee, Dr.rer.nat
Staff Scientist and Engineer
Lawrence Berkeley National Laboratory
1 Cyclotron Road Mailstop 46R0161
Berkeley, CA 94720, United States
Tel :+1-510-486-6163
Cell:+1-510-384-3868

References:
Issue with RULES_BUILD of seq 2.2.9 NICOLE Remi via Tech-talk

Navigate by Date:
Prev: Re: ai - record unfortunately does not behave as I expect it to Heinz Junkes via Tech-talk
Next: IOC file for motorMicronix MMC200 Jong Woo Kim via Tech-talk
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  <20222023  2024 
Navigate by Thread:
Prev: Re: Issue with RULES_BUILD of seq 2.2.9 Ralph Lange via Tech-talk
Next: Rocky Linux 8 RPMs Abdalla Ahmad via Tech-talk
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  <20222023  2024 
ANJ, 14 Sep 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·