Re: epicsThreadOpts undeclared identifier windows build error

["Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov>]

Hi Kevin,

epicsThreadCreateOpt() was added in EPICS 7.0.3.1, it wasn’t present in EPICS 3.15. See https://epics.anl.gov/base/R7-0/3-docs/RELEASE_NOTES.html for the description. You’ll have to disable CI builds of that module against 3.15.

- Andrew

-- 

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

On 1/23/26, 2:10 PM, "Tech-talk" <tech-talk-bounces at aps.anl.gov> wrote:

I'm trying to resolve some Windows github actions build errors in the motorAttocube module and I'm very confused.  I apologize in advance for all the mangled URLs.

The "3.15 Win VS2022, static" build of "ci build fixes #13" of motorAttocube fails with an error that epicsThreadOpts is undeclared:

D:\a\motorAttocube\motorAttocube\attocubeApp\src\motorAttocubeDriver.cc(356): error C2065: 'epicsThreadOpts': undeclared identifier

source: https://gcc02.safelinks.protection.outlook.com/?url="">

motorAttocubeDriver.cc is including epicsThread.h:

https://gcc02.safelinks.protection.outlook.com/?url="">

which is where epicsThreadOpts is declared:

https://gcc02.safelinks.protection.outlook.com/?url="">

The AttocubeController constructor is where the error occurs:

https://gcc02.safelinks.protection.outlook.com/?url="">

The driver is calling epicsThreadCreateOpt to make the thread joinable.  Most other motor drivers call epicsThreadCreate instead.

Is something else needed on Windows in addition to including epicsThread.h to make this work?

Thanks,

Kevin