SYS-OSS/FRET-qemu
4
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs/system: Use the meson binary from the pyvenv

Browse Source 
To avoid problems with the meson installation from the host
system, we should always use the meson from our venv instead.
Thus use this in the documentation, too.

While we're at it, also mention that it has to be run from
the build folder (in the igb.rst file; the other two files
were already fine).

Suggested-by: Niek Linnenbank <nieklinnenbank@gmail.com>
Message-ID: <20250318055415.16501-1-thuth@redhat.com>
Reviewed-by: Akihiko Odaki <akihiko.odaki@daynix.com>
Reviewed-by: Niek Linnenbank <nieklinnenbank@gmail.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
This commit is contained in:
Thomas Huth 2025-03-18 06:54:15 +01:00
parent 23686dfb76
commit cef6da5bc9
3 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/system/arm/bananapi_m2u.rst
View File

@ -136,4 +136,4 @@ provide the following command:
$ cd qemu-build-dir
$ QEMU_TEST_ALLOW_LARGE_STORAGE=1 \
meson test --suite thorough func-arm-arm_bpim2u
pyvenv/bin/meson test --suite thorough func-arm-arm_bpim2u

2
docs/system/arm/orangepi.rst
View File

@ -262,4 +262,4 @@ provide the following command from the build directory:
.. code-block:: bash
$ QEMU_TEST_ALLOW_LARGE_STORAGE=1 \
meson test --suite thorough func-arm-arm_orangepi
pyvenv/bin/meson test --suite thorough func-arm-arm_orangepi

5
docs/system/devices/igb.rst
View File

@ -57,11 +57,12 @@ directory:
meson test qtest-x86_64/qos-test
ethtool can test register accesses, interrupts, etc. It is automated as an
functional test and can be ran with the following command:
functional test and can be run from the build directory with the following
command:
.. code:: shell
meson test --suite thorough func-x86_64-netdev_ethtool
pyvenv/bin/meson test --suite thorough func-x86_64-netdev_ethtool
References
==========