This is the symptom of a polyspace-configure issue related to a Cygwin's executable like "make.exe" or "tee.exe", executable used during the build process.
A workaround is to create the missing folder and copy the file "ps_windows_dllinject.dll" (that can be found in <Polyspace installation>/polyspace/configure/win64) into this new folder.
To know the folder to create, you can use the tool Process Monitor (from Microsoft) to see which paths are being referenced during the build process.
To help you apply this workaround, a predefined filter for Process Monitor, specifically targeting the location of the DLL, is attached to this article.
Here is the procedure:
- Download Process Monitor: https://learn.microsoft.com/en-us/sysinternals/downloads/procmon#download
- Launch the tool and choose the menu "Filter / Organize Filters"
- Import the file "configure inject.PMF" in attachment
- Now, choose the menu "Filter / Load Filter" then "configure inject", the filter will be applied
- In the results, take a look at the column "Path" to know where ps_windows_dllinject.dll should be copied.
