Allen Byrne
Allen Byrne
Note that I did use the latest 3.3.1 version however everything worked with the define on the command line ` -Dhdfview.workdir="$PWD"`
The launcher worked (after edit) without any other changes. However, the supplied hdfview.sh does need to set the the INSTALLDIR up two dirs from the .sh location (export INSTALLDIR=$dir/../..).
I don't think this workdir process changed from 3.3.0 but I will check. There are two ways to invoke HDFView, from the launcher in the $INSTALLDIR/bin folder or the script...
Looks like we fixed the workdir option in 3.3.1 and forgot to announce it in the release notes. Please try 3.3.1.
> and it does not appear to be looking for an HDFview.cfg file: The shell script would not use the .cfg, only the launcher binary. I'm guessing you appending the...
Actually, have you tried to add the "-start=$PWD" to the command; ... hdf.view.HDFView -start="$PWD" "$@"
See WorkingDirectory.txt for a description of arguments to HDFView. (-start is at line 16)
The simple workaround is to add "$PWD" to the "$@" -> "$PWD/$@"
Will try to fix it in the next release this spring as it looks like it is an implementation bug. It seems to not consider the startDir setting(looks like multiple...
Looks like t_cache_image test hung.