Hi Alan,
> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Thursday, December 22, 2016 7:31 PM
> To: Arjen Markus
> Cc: PLplot development list
> Subject: An alternative idea for comprehensive testing of MSVC + ifort
>
> On 2016-12-22 09:32-0000 Arjen Markus wrote:
>
> [...]
> > I now use a Tcl script to compare the files (because of lack of a
> > suitable command under Windows - sigh)
> [...]
>
> Hi Arjen:
>
> I got curious about that, and a google search found
> <http://stackoverflow.com/questions/6877238/what-is-the-windows-equivalent-of-
> the-diff-command>
> where some of the suggested windows equivalents of the diff command seemed to
> meet with universal approval.
>
> The problem is that is a start of a long difficult path where you end up
> trying to
> mimic the logic of our current test system that depends on bash and several
> other
> Unix tools (such as cmp and/or diff).
>
Well, the script I have now simply skips the first fews lines (which contain
the timestamp) and then compares the rest of the two files as two long strings.
So the C equivalent would be fairly short as well. And nothing at all like cmp
and diff. It simply tells the user whether the files have different lengths or
whether the contents are different.
>
> I am pretty confident this approach would work because it is equivalent to the
> approach I used to take for testing the old MinGW (without old MSYS) build
> that
> used the "MinGW Makefiles" generator on the Wine version of Windows. All those
> tests were done from a CMD environment using the old MinGW make command
> (mingw32-make.exe) but with the old MSYS bin directory on the PATH to give
> access to the Unix tools needed for the tests (but avoiding using those tools
> for the
> build itself). So I don't see why you cannot do the same with nmake.exe
> replacing
> mingw32-make.exe.
>
> In sum, I recommend you take another serious look at this general approach
> (with
> Unix tools used just for testing but expressly not used for the build) the
> next time
> (likely in 2017) that you have a chance to work on PLplot testing on the MSVC
> +
> ifort build platform.
>
I will do that - the drawback would be that the user needs to have MinGW
installed in some form. Also it may not be all that evident where the MinGW
tools are installed. Still, worth a try.
Regards,
Arjen
DISCLAIMER: This message is intended exclusively for the addressee(s) and may
contain confidential and privileged information. If you are not the intended
recipient please notify the sender immediately and destroy this message.
Unauthorized use, disclosure or copying of this message is strictly prohibited.
The foundation 'Stichting Deltares', which has its seat at Delft, The
Netherlands, Commercial Registration Number 41146461, is not liable in any way
whatsoever for consequences and/or damages resulting from the improper,
incomplete and untimely dispatch, receipt and/or content of this e-mail.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
