Hi,
We predominantly work with the PLCNext in C++ and I routinely find the following steps tend to take a bit of time (even if there are no relevant changes) :
plcncli generate code --verbose
plcncli generate config --verbose
* I am looking for simple ways to try and optimise this and have the following questions : The simplest method I have so far is to not bother running these commands if I know that I have run them in the past and nothing GDS related has changed. Is this about right ? Extending on this, writing a script that prevents these steps from running if nothing relevant in all project associated headers is likely to be my next step.
* Are there any other ways you know to optimise this step in the process ?
Hi Lindsay.
Just getting back to these questions after discussions with the developers.
The answers to your two questions are “yes” and “no (sorry)”.
Basically, the plcncli tool is trying to help out by auto-generating some source files and configuration files in the project. Adding checks to this process - to decide if re-generating these files is necessary - probably wouldn’t end up saving much time. In theory it’s possible for you to maintain those auto-generated files yourself as the project evolves, in which case you wouldn’t ever need to run those two generate commands during the build.
Martin,
Thanks for getting back to me about this. I suspected the second answer was no, but thanks for asking. I will give option 1 a go as mentioned with a simple bash script. In some instances I have been doing this manually in the past and it does save a fair bit of time in compilation, but you have to be careful/diligent.
Cheers,
Lindsay