EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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: Sequencer configuration file
From: Andrew Johnson via Tech-talk <tech-talk at aps.anl.gov>
To: "David A. Slimmer" <slimmer at fnal.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Tue, 18 Apr 2023 13:28:35 -0500
Hi David,

On 4/18/23 12:47 PM, David A. Slimmer via Tech-talk wrote:

After a long hiatus I’m working with EPICS again, so I imagine some things may have changed.

Welcome back then!

Which appears to be the %{ code }% being compiled with gcc instead of g++.

 

Is there a way to configure this via one of the configuration files to have this sequencer code compiled with g++?

Some things have not changed, one of which is that the SNL compiler generates C code, and I don't know if anyone has tried using a C++ compiler on its output. That doesn't mean it won't work, but it will need some tweaking of the build system at least to do that.

The first thing I would try would be to change the seq/configure/RULES_BUILD file which has 2 pattern rules with the target %.c — you could try changing them to %.cpp and the build system should then name the intermediate file as .cpp and use the C++ compiler to build it.

Beyond that you'd need to discuss any other necessary changes with Benjamin Franksen who is the maintainer of the sequencer. He may ask you to work on the latest release for any changes that you want to push upstream. I could see it being relatively easy to add a Makefile variable to control what extension the generated files use, but if the code generation needs to change at all that would be a different level of complexity.

- Andrew
-- 
Complexity comes for free, Simplicity you have to work for.
Replies:
Re: Sequencer configuration file Michael Davidsaver via Tech-talk
References:
Sequencer configuration file David A. Slimmer via Tech-talk
Navigate by Date:
Prev: Sequencer configuration file David A. Slimmer via Tech-talk
Next: Re: asynInterposeEos/StreamDevice: "read from low-level driver returned 1" and EAGAIN/EWOULDBLOCK Érico Nogueira Rolim 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  2022  <2023>  2024 
Navigate by Thread:
Prev: Sequencer configuration file David A. Slimmer via Tech-talk
Next: Re: Sequencer configuration file Michael Davidsaver 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  2022  <2023>  2024 
ANJ, 18 Apr 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·