Doesn't work with the GHDL Snap package

[interfect]

When I have GHDL installed as a Snap, trying to run my run.py gives me:

Compiling into dcpu16_lib:      src/andgate.vhd                                                                                              passed
Compiling into vunit_lib:       ../../../.local/lib/python3.10/site-packages/vunit/vhdl/string_ops/src/string_ops.vhd                        failed
=== Command used: ===
/snap/bin/ghdl -a --workdir=/home/myusername/workspace/cat-fpga/dcpu16-core/vunit_out/ghdl/libraries/vunit_lib --work=vunit_lib --std=08 -P/home/myusername/workspace/cat-fpga/dcpu16-core/vunit_out/ghdl/libraries/vunit_lib -P/home/myusername/workspace/cat-fpga/dcpu16-core/vunit_out/ghdl/libraries/dcpu16_lib -P/home/myusername/workspace/cat-fpga/dcpu16-core/vunit_out/ghdl/libraries/dcpu16_test_lib /home/myusername/.local/lib/python3.10/site-packages/vunit/vhdl/string_ops/src/string_ops.vhd


=== Command output: ===
/snap/ghdl/1/bin/ghdl: cannot open /home/myusername/.local/lib/python3.10/site-packages/vunit/vhdl/string_ops/src/string_ops.vhd

Compile failed

I think the Snap confinement is not allowing the sandboxed GHDL to access that file, even though it is being passed in in the command line.

If I replace the GHDL Snap with GHDL from the real package manager, it works.

[LarsAsplund]

@interfect Unfortunately, I don't have any experience with Snap but from what I understand, Snap provides a sandbox in which an application runs. A sandbox should always be in control over what an application can and cannot access so this feels like something that is and should be out of reach for VUnit.