Re: [Plplot-devel] Comprehensive testing: MinGW/MSYS

2015-04-20 Thread Alan W. Irwin
On 2015-04-20 21:18-0700 Greg Jung wrote: > Alan, > Since these strings that are kept in files, that need to be > associated with each possible driver, > do not change over the years, why maintain a separate location? Why > not just compile those strings > into the body of plplot.obj? The incr

Re: [Plplot-devel] Comprehensive testing: MinGW/MSYS

2015-04-20 Thread Greg Jung
Alan, Since these strings that are kept in files, that need to be associated with each possible driver, do not change over the years, why maintain a separate location? Why not just compile those strings into the body of plplot.obj? The increase of data size will probably be balanced by the dec

Re: [Plplot-devel] Comprehensive testing: MinGW/MSYS

2015-04-20 Thread Alan W. Irwin
On 2015-04-20 13:27-0700 Alan W. Irwin wrote: > On 2015-04-20 12:55-0700 Alan W. Irwin wrote: > >> Furthermore -debug works fine for me on MinGW/MSYS/Wine, but the only >> extra output from it comes after the device is selected from the list >> above. So to debug further you will have to (locally)

[Plplot-devel] Commit id c44f636

2015-04-20 Thread Alan W. Irwin
Hi Andrew: Commit id c44f636 makes a substantial hack to plparseopts so that the -debug option now works for any code (e.g., plInitDispatchTable) that is called by pllib_init. The result passes substantial testing (valgrind, test_noninteractive, and test_interactive) on Linux, but you are much mo

Re: [Plplot-devel] Comprehensive testing: MinGW/MSYS

2015-04-20 Thread Alan W. Irwin
On 2015-04-20 12:55-0700 Alan W. Irwin wrote: > Furthermore -debug works fine for me on MinGW/MSYS/Wine, but the only > extra output from it comes after the device is selected from the list > above. So to debug further you will have to (locally) add informative > pldebug calls to the code near whe

Re: [Plplot-devel] Comprehensive testing: MinGW/MSYS

2015-04-20 Thread Alan W. Irwin
On 2015-04-20 14:57- Arjen Markus wrote: > Hi Alan, > > > >> -Original Message- >> From: Alan W. Irwin [mailto:[email protected]] >> >> Then attempt to run the built example once with PLPLOT_DRV_DIR set to above >> and once with PLPLOT_DRV_DIR set to nothing (PLPLOT_DRV_DIR=).

Re: [Plplot-devel] Comprehensive testing: MinGW/MSYS

2015-04-20 Thread Arjen Markus
Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:[email protected]] > > Then attempt to run the built example once with PLPLOT_DRV_DIR set to above > and once with PLPLOT_DRV_DIR set to nothing (PLPLOT_DRV_DIR=). > > examples/c/x00c -debug -dev psc -o test.psc 2>&1 |\

Re: [Plplot-devel] Comprehensive testing: MinGW/MSYS

2015-04-20 Thread Alan W. Irwin
Hi Arjen: On 2015-04-20 11:31- Arjen Markus wrote: > Hi Alan, > > > > I added the option "-do_clean_as_you_go no" to the test script. The result is attached. Hopefully this will shed some light on the anomalies MinGW/MSYS is causing. My updated script appears not to be capturing the script

Re: [Plplot-devel] Comprehensive testing: Cygwin

2015-04-20 Thread Alan W. Irwin
On 2015-04-20 06:45- Arjen Markus wrote: > Hi Alan, > > > >> -Original Message- >> From: Alan W. Irwin [mailto:[email protected]] >> >> That is good news indeed. So it appears we finally have a good baseline >> result for >> Cygwin without any brute force changes. >> I am wel