From 8ff587cb83a79f392fa5314ac73839be512ed5a7 Mon Sep 17 00:00:00 2001
From: Tristan Gingold <tgingold@free.fr>
Date: Wed, 1 Nov 2017 06:25:42 +0100
Subject: Improve testsuite/gna README.

---
 testsuite/gna/README | 22 ++++++++++++++++++++--
 1 file changed, 20 insertions(+), 2 deletions(-)

diff --git a/testsuite/gna/README b/testsuite/gna/README
index f2489f91a..37155ad33 100644
--- a/testsuite/gna/README
+++ b/testsuite/gna/README
@@ -19,7 +19,25 @@ Here are some tips for portability.
   compare expected output with a reference file.
 - don't forget that executable files have a .exe suffix on windows, but most
   cygwin tools transparently add the suffix.
-- For VPI tests, the directory containing the dll file must be added in PATH.
-  See issue98 for an example.
 - As a last resort, you can test if you are on Windows:
   if [ "$OS" = "Windows_NT" ]; then ...
+
+
+VPI tests: on windows the directory containing the DLL file must be added in
+PATH. From issue98:
+--------------------------------------------------
+if [ "$OS" = "Windows_NT" ]; then
+    vpi_lib=`$GHDL --vpi-library-dir | sed -e 's!\\\\!/!g' -e 's!^C:!/C!g'`
+    echo vpi_lib: $vpi_lib
+    PATH="$PATH:$vpi_lib"
+fi
+--------------------------------------------------
+
+GHDL could be configured without wave dump support. If you need to test ghw,
+you should test if the feature is supported.  From issue158:
+--------------------------------------------------
+if ghdl_has_feature repro ghw; then
+  simulate repro --wave=repro.ghw
+  # How to test the ghw ?  Use ghwdump ?
+fi
+--------------------------------------------------
-- 
cgit v1.2.3