Can you have multiple UVVM releases side by side

Hi,

A bit related to my previous question.
Can you compile multiple UVVM releases side by side?
Say version x, y and z.

And how to select these in your project then?

Rgds,
Eric

Hi,
It is not possible to have several compilations of UVVM in one single directory (without lots of modifications that is). Are there any reason why you would like to do this?

Br,
Marius

Hi,

Perhaps I didn’t express myself clear.

Say that our development server has version 2019.x of UVVM installed.

I would like to have this compiled into a folder UVVM_2019.x.

How to do that?

And projectA from 2019 has used this folder with a mapping called UVVM.

And a check in the testbench (see other post) that this is version 2019.x.

ProjectB starts from scratch this year and is using version 2020.y of UVVM.

On our development server has version 2020.y of UVVM is also installed, side by side with version 2019.x.

I would like to have this compiled into a folder UVVM_2020.y.

And projectB uses this folder with a mapping also called UVVM, just like projectA.

And a check in the testbench (see other post) that this is version 2020.y.

And say that we have ProjectC that used 2019.x but needs an update.

And therefor needs version 2020.y of UVVM is wanted/needed.

As they are side by side I want to remap UVVM from 2019.x to 2020.y.

This makes it possible that:

  • ProjectA still can use 2019.x,
  • and if somehow the UVVM path is not pointing to 2019.x incorrect, I can generate a warning in the testbench. (see other post)- ProjectB can use the 2020.y
  • ProjectC can be migrated from 2019.x to 2020.y

Is this way of working facilitated in the UVVM library?

Rgds,

Eric