06-14-2018 11:40 PM - edited 06-14-2018 11:42 PM
Hi, when I upgraded from 2016.4 to 2017.2 I noticed that the codegenerator in the SDK will use the latest version of the libraries instead of the one given in .mld,mss and the handwritten .tcl I use to create our application.
Is there a way to stop the generator to select the latest library?
The result is that I got two versions of some libraries and the later seems to be just copied without the generation step.
(We have qualified the software in one configuration of libraries and don't want to be "upgraded" without control)
I want to introduce later versions but don't want to break old code .
06-15-2018 12:18 AM
I just tried the same use case mentioned by you. Found that in BSP settings, I am seeing two versions of the libraries (which is expected). But the one which is created in earlier release will have the older version of libraries.
Please check the attached screenshot for more clarity.
please add your screenshot.
Thanks & Regards,
Praveen Kumar. V
06-15-2018 12:09 PM
Ok, in my case I used a application under sw_apps like the fsbl or hello world.
I will test to set the standalone version too (OS) and the other libraries and see what happens.