UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Visitor patsv99
Visitor
530 Views
Registered: ‎06-14-2018

Version handling of libraries

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 .

Regards

// Patrik

 

0 Kudos
2 Replies
Xilinx Employee
Xilinx Employee
517 Views
Registered: ‎01-03-2017

Re: Version handling of libraries

Hi @patsv99,

 

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

bsp.png
0 Kudos
Visitor patsv99
Visitor
483 Views
Registered: ‎06-14-2018

Re: Version handling of libraries

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.

Regards
// Patrik

0 Kudos