vunit work library issue

[jezbaker110]

I have an issue where I have tried to list all my project files in the python script. However the code has some IP files which reference packages in a work library. I cannot change the IP code. Vunit is saying it cannot find these files. Vunit will not let me compile these files into a work library, so I am not sure how to get around this issue. It not allowing the design to be compiled. I have checked the modelsim.ini file and no reference has been made to the work library.

[eine]

The work library is a special name in VHDL which means 'the same library where this element is defined'. If you compile a module A to library 'lib' and it uses work.B, then module B must also be compiled to library 'lib'.

https://insights.sigasi.com/tech/work-not-vhdl-library.html

[kraigher]

The question was answered by @1138-4eb

[jezbaker110]

I have tried compiling these pkg files into another library but then when vunit compiles the code, it throws up an error because it cannot find these files in the work library being referenced.

[eine]

Almost all the examples instantiate components from work. You can have a look at them as a reference. Apart from that, it is really hard to guess a solution, if you don't help us by providing some detailed info about your use case. Can you provide a MWE? Or, at least, the run.py that you are using and the error message you get?

[jezbaker110]

I was just using the normal method in my run.py file from os.path import join, dirname from vunit import VUnit root = dirname(__file__) ui = VUnit.from_argv() lib = ui.add_library("lib") lib.add_source_files(join(root, "*.vhd")) The error was telling me that it could not find the library work. This was when it compiled a file was referencing a pkg file in the library work. My modelsim.ini file made no reference to the work library.

…

Sent from my iPhone

On 26 May 2019, at 13:18, 1138-4EB ***@***.***> wrote: Almost all the examples instantiate components from work. You can have a look at them as a reference. Apart from that, it is really hard to guess a solution, if you don't help us by providing some detailed info about your use case. Can you provide a MWE? Or, at least, the run.py that you are using and the error message you get? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[eine]

That sounds as a problem with the compilation order. Since you are compiling all the sources to the same library, all the components must be found unless i) it was not compiled before or ii) some error was produced while it was being compiled. Please, check the log to ensure that the offending module has not been compiled. If so, rewrite the run.py to add sources explicitly in an order which you know that will work. If this solves your issue, please open a new PR about why the order is not properly picked for you design.

[jezbaker110]

Thanks for the reply. I thought the same thing and tried to compile the pkg files first, using the order that I know works when just compiling into modelsim, but I still had issues.

…

Sent from my iPhone

On 26 May 2019, at 14:02, 1138-4EB ***@***.***> wrote: That sounds as a problem with the compilation order. Since you are compiling all the sources to the same library, all the components must be found unless i) it was not compiled before or ii) some error was produced while it was being compiled. Please, check the log to ensure that the offending module has not been compiled. If so, rewrite the run.py to add sources explicitly in an order which you know that will work. If this solves your issue, please open a new PR about why the order is not properly picked for you design. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[LarsAsplund]

@jezbaker110 We need to see some logs and code to support you on this.