At the moment the galil driver cannot be built on anything other than VS 2010, but the TWINCAT ioc doesn't build on 2010.
This is a problem, for example on CRISP where we seem to have released a 2010 build and then patched on the twincat ioc and all of it's 2017 DLLs. This setup doesn't seem to be documented anywhere and will break next time we do a release.
As a developer I would like Jenkins to be able to build a single consistent release without the need for individual IOCs to be patched later.
Possible solutions:
Do the "new galil driver" ticket so that we can deploy a VS2017 build
At the end of a normal release build, copy the twincat IOC and it's DLLs into the release from a share (essentially what appears to have been done on CRISP, but automated)
At the moment the galil driver cannot be built on anything other than VS 2010, but the TWINCAT ioc doesn't build on 2010.
This is a problem, for example on CRISP where we seem to have released a 2010 build and then patched on the twincat ioc and all of it's 2017 DLLs. This setup doesn't seem to be documented anywhere and will break next time we do a release.
As a developer I would like Jenkins to be able to build a single consistent release without the need for individual IOCs to be patched later.
Possible solutions: