Re: synApps quadEM build-time code generation

[Iain Marcuson via Tech-talk <tech-talk at aps.anl.gov>]

My IOC has quite a few parameters that can be described for our purposes as basically (name, register number, type, bitmask, scale and offset parameter) tuples.  I have a Python script I run before compilation that turns those entries into database files and C++ entries.  I then run the standard `make` to build the IOC.  One possibility I see is for the build process to run that Python script and move the output files as a prelude to the compilation.

---

From: Johnson, Andrew N. <anj at anl.gov>
Sent: Friday, October 11, 2024 2:27:37 PM
To: Iain Marcuson; tech-talk at aps.anl.gov
Subject: Re: synApps quadEM build-time code generation

 

Hi Iain,

 

The EPICS build system does quite a lot of code generation, GNUmake handles that well. I think you’ll need to explain a bit more about what’s different about your process (what does it need to do?) for us to be able to suggest some answers.

 

- Andrew

 

-- 

Complexity comes for free, Simplicity you have to work for.

 

 

On 10/11/24, 1:17 PM, "Tech-talk" <tech-talk-bounces at aps.anl.gov> wrote:

 

I am looking to submit a pull request to incorporate a new quadEM IOC into the official package.  The build process uses code-generation, and I don’t see an obvious way to invoke that at build time.  Alternatively, I could generate and commit the code, then send a pull request for that, if that would be better, but I would definitely also want to include the template files used as a basis for the generated code.  What approach would be best for this submission?

 

Thank you,

 

Iain Marcuson.

 

This message has been scanned for malware by Forcepoint. www.forcepoint.com

Click here to report this email as spam.