I've re-checked my plplot tree with cygwin which completed the
comprehensive test earlier,
it does not have an issue with the build.
On Tue, Jul 14, 2015 at 10:07 PM, Alan W. Irwin <ir...@beluga.phys.uvic.ca>
wrote:
> On 2015-07-14 18:30-0700 Greg Jung wrote:
>
> I'm working on it, from my point of view (which includes examining the
>> "installed" perspective).
>> I've had now since I adopted Msys2, a well-working cmake system that
>> applies equally to mingw/msys,
>> mingw32/msys2, and mingw64/msys. All with the standard cmake executable
>> and with only a few
>> module replacements.
>>
>
> Hi Greg:
>
> I appreciate your willingness to do more testing. However, I frankly
> am guessing a bit about exactly what you meant above because of your
> notation for the various platforms and possibly a typographical error
> in your notation as well. The problem with your notation is it is
> inconsistent with the actual properly capitalized names of the
> component projects which are MinGW, MSYS, MinGW-w64, and MSYS2. An
> additional complication is MinGW, and MSYS come only in 32-bit form
> while MinGW-w64, and MSYS2 come in both 32-bit and 64-bit form. So I
> think the notation for the relevant combinations should be MinGW/MSYS
> for the classical platform you get when you use the MinGW installer
> mentioned in the wiki for the <sf.net/projects/mingw> project and the
> designation 32-bit or 64-bit MinGW-w64/MSYS2 for the platform you get
> when you use the MSYS2 "pacman" installer mentioned in the wiki for
> the <sf.net/projects/msys2> project.
>
> So I assume your mingw/msys is actually MinGW/MSYS, your mingw32/msys2
> is actually 32-bit MinGW-w64/MSYS2, and your mingw64/msys (although
> you probably meant to type mingw64/msys2) is actually 64-bit
> MinGW-w64/MSYS2.
>
> If that assumption is correct, and you really are already testing the
> "vanilla" 64-bit MinGW-w64/MSYS2 platform as defined specifically
> above rather than some variant of that you got from elsewhere which
> likely does not have the popularity and heavy user testing that the
> vanilla version receives, then I am very interested in your
> comprehensive test report for that platform.
>
> As you know it typically takes several iterations to get such test
> reports perfected, but once that is done, and assuming you are still
> game for additional testing, then obtaining a perfected test report
> for the 32-bit version of MinGW-w64/MSYS2 should be worth doing as
> well. But I strongly suggest you concentrate just on the 64-bit
> version of MinGW-w64/MSYS2 to start with to see how that goes.
>
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state
> implementation for stellar interiors (freeeos.sf.net); the Time
> Ephemerides project (timeephem.sf.net); PLplot scientific plotting
> software package (plplot.sf.net); the libLASi project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
> and the Linux Brochure Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
>
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
