Just to confirm - everything seems to work fine on Cygwin too
Phil
       From: phil rosenberg <philip_rosenb...@yahoo.com>
 To: Arjen Markus <arjen.mar...@deltares.nl> 
Cc: "plplot-devel@lists.sourceforge.net" <plplot-devel@lists.sourceforge.net> 
 Sent: Tuesday, 7 October 2014, 9:30
 Subject: Re: [Plplot-devel] Testing on Windows (line endings for bash scripts)
   
Thanks ArjenAlan (also I just saw your latest email) - I have tested your 
changes and they work on my Windows system. I must confess that I didn't think 
they would. However, perhaps the important thing that I change in the script 
were a couple of lines that looked something like
cd ${OUTPUT_DIRECTORY}result=`pwd | sed  s '?some?regex?replace?'
to something like result=${OUTPUT_DIRECTORY}#some ifs and sed commands
Removing the cd and pwd calls allowed path changes from CMake to propagate 
correctly. I guess that I made the logic changes with that still in place in 
case it was important, then decided to take it out as I couldn't see its use.
Your command of CMake is significantly better than mine so I guess I naturally 
move towards doing things in shell scripts where I'm a bit more efficient.
I was just trying to test things on Cygwin as it should presumably be 
relatively simple to build in Cygwin, however, when I try to clone the 
repository I keep getting disconnected. I'll let you know if I get this done.
Phil
  

     From: Arjen Markus <arjen.mar...@deltares.nl>
 To: phil rosenberg <philip_rosenb...@yahoo.com> 
Cc: "plplot-devel@lists.sourceforge.net" <plplot-devel@lists.sourceforge.net> 
 Sent: Tuesday, 7 October 2014, 7:59
 Subject: RE: [Plplot-devel] Testing on Windows (line endings for bash scripts)
   
#yiv5405376081 -- filtered {font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 
4;}#yiv5405376081 filtered {font-family:SimSun;panose-1:2 1 6 0 3 1 1 1 1 
1;}#yiv5405376081 filtered {font-family:SimSun;panose-1:2 1 6 0 3 1 1 1 1 
1;}#yiv5405376081 filtered {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 
4;}#yiv5405376081 filtered {panose-1:2 1 6 0 3 1 1 1 1 1;}#yiv5405376081 
p.yiv5405376081MsoNormal, #yiv5405376081 li.yiv5405376081MsoNormal, 
#yiv5405376081 div.yiv5405376081MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv5405376081 a:link, 
#yiv5405376081 span.yiv5405376081MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv5405376081 a:visited, #yiv5405376081 
span.yiv5405376081MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv5405376081 p 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv5405376081 
p.yiv5405376081MsoAcetate, #yiv5405376081 li.yiv5405376081MsoAcetate, 
#yiv5405376081 div.yiv5405376081MsoAcetate 
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;}#yiv5405376081 
span.yiv5405376081BalloonTextChar {}#yiv5405376081 p.yiv5405376081msoacetate, 
#yiv5405376081 li.yiv5405376081msoacetate, #yiv5405376081 
div.yiv5405376081msoacetate 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv5405376081 
p.yiv5405376081msonormal, #yiv5405376081 li.yiv5405376081msonormal, 
#yiv5405376081 div.yiv5405376081msonormal 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv5405376081 
p.yiv5405376081msochpdefault, #yiv5405376081 li.yiv5405376081msochpdefault, 
#yiv5405376081 div.yiv5405376081msochpdefault 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv5405376081 
p.yiv5405376081msonormal1, #yiv5405376081 li.yiv5405376081msonormal1, 
#yiv5405376081 div.yiv5405376081msonormal1 
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv5405376081 
p.yiv5405376081msoacetate1, #yiv5405376081 li.yiv5405376081msoacetate1, 
#yiv5405376081 div.yiv5405376081msoacetate1 
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;}#yiv5405376081 
p.yiv5405376081msochpdefault1, #yiv5405376081 li.yiv5405376081msochpdefault1, 
#yiv5405376081 div.yiv5405376081msochpdefault1 
{margin-right:0cm;margin-left:0cm;font-size:10.0pt;}#yiv5405376081 
span.yiv5405376081msohyperlink {}#yiv5405376081 
span.yiv5405376081msohyperlinkfollowed {}#yiv5405376081 
span.yiv5405376081emailstyle18 {}#yiv5405376081 span.yiv5405376081msohyperlink1 
{color:blue;text-decoration:underline;}#yiv5405376081 
span.yiv5405376081msohyperlinkfollowed1 
{color:purple;text-decoration:underline;}#yiv5405376081 
span.yiv5405376081emailstyle181 {color:black;}#yiv5405376081 
span.yiv5405376081EmailStyle32 {color:#1F497D;}#yiv5405376081 
.yiv5405376081MsoChpDefault {font-size:10.0pt;}#yiv5405376081 filtered 
{margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv5405376081 
div.yiv5405376081WordSection1 {}#yiv5405376081 Hi Phil,    Rest assured – I 
have these test environments up and running and that is how I will go about 
testing the stuff. (I have been bitten by the inadvertent combination of 
components from different environments myself – in my case: 32-bits and 64-bits 
combinations, that is no fun either, as it took me some time to realise this 
was going on.)    Regards,    Arjen       

From: phil rosenberg [mailto:philip_rosenb...@yahoo.com]
Sent: Tuesday, October 07, 2014 8:50 AM
To: Arjen Markus; Alan W. Irwin
Cc: plplot-devel@lists.sourceforge.net
Subject: Re: [Plplot-devel] Testing on Windows (line endings for bash scripts)  
  Hi this is just a quick email - I will reply properly later today    I think 
the tests in the shell script are necessary - I am building natively under 
windows - that is the whole point - so I am using native Windows CMake and Tcl. 
However the test scripts are run with Bash. Cmake automatically detects my 
Cygwin Bash - presumably if I had MSys it would find Msys Bash. The point being 
that the tests are run under a different environment to the build. To get the 
correct path I need to find the environment that the tests are run under and 
the only way to do that 100% reliably is to do it in the shell script.    As I 
said I made every effort possible to maintain current behaviour for MSys and 
Cygwin builds, I just don't have those environments fully set up with Plplot so 
I hoped that if someone had then it would be an easy job for them to test.    
Phil
   From: Arjen Markus <arjen.mar...@deltares.nl>
To: Alan W. Irwin <ir...@beluga.phys.uvic.ca>; phil rosenberg 
<philip_rosenb...@yahoo.com>
Cc: "plplot-devel@lists.sourceforge.net" <plplot-devel@lists.sourceforge.net>
Sent: Tuesday, 7 October 2014, 7:35
Subject: RE: [Plplot-devel] Testing on Windows (line endings for bash scripts)  
  Hi Alan, Phil,   I will test Tcl under the various Windows environments. I am 
– in hindsight – not surprised by Phil’s difficulties with the path names: -    
    Bare Windows, MSYS and Cygwin each use a different method to indicate the 
drive, where the culprit is the conflict between the colon used by Windows to 
separate the drive letter and the colon used by UNIX-like environments to 
separate paths in the PATH variable. -        The space in the directory names 
only adds extra complexity that is even more pervasive. Just think about 
separating command-line arguments.   When you use Cygwin, then you definitely 
need to use the Cygwin version of Tcl. For MSYS things are more complicated, as 
that is part of the minimal UNIX-like or should I say GNU-like environment, so 
comes with preciously few packages.   Regards,   Arjen          > -----Original 
Message-----
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Tuesday, October 07, 2014 6:56 AM
> To: phil rosenberg
> Cc: plplot-devel@lists.sourceforge.net; Arjen Markus
> Subject: Re: [Plplot-devel] Testing on Windows (line endings for bash scripts)
>
> On 2014-10-06 11:56-0700 Alan W. Irwin wrote:
>
> > Hi Phil:
> >
> > I strongly recommend that you modify your recent changes so they only
> > apply for the MSVC platform [...]
>
> @ Phil: Never mind, I did that myself with commit 5dd59cb.  Please try
>
> git diff --ignore-all-space 5dd59cb^..5dd59cb
>
> to see the actual non white-space changes I did in this commit and also look 
> at the
> 5dd59cb commit message for several important caveats.
>
> Please test my commit for the MSVC case to confirm I left in everything 
> essential for
> that case (see caveats about the cd commands in the above commit message which
> may require further changes from you if the tcldir variable is being set to 
> the wrong
> value for MSVC).
>
> Also, please test the Cygwin platform with the Cygwin version of CMake (if an
> incorrect CMake version was your prior issue) to see if you can confirm the 
> good
> results that Arjen obtained before for that platform for the tcl case. And 
> similarly test
> the MSYS platform (this time for the native Windows version of CMake) if you 
> have
> time.
>
> @Arjen: Please test Tcl on both the Cygwin and MSYS platforms to make sure no
> build-system regressions have crept in since your last successful tests on 
> those
> platforms.
>
> @Both of you: I prefer not to do comprehensive MSYS tests very often because 
> they
> take roughly 20 times longer (i.e., several days rather than several hours) 
> to do on
> the Wine version of Windows I have access to compared to the Microsoft 
> version of
> Windows that you guys have access to.  However, the last comprehensive tests 
> I did
> on Wine were perfect, and I don't think anything bad has been introduced into 
> the
> build system (at least in its current state for commit 5dd59cb) for the MSYS 
> platform
> since that success.  So the tests I have requested from you guys for MSYS 
> should
> also be perfect if you have no blanks in paths.
>
> @Phil: note that my test of a blank in the build-tree path for the "test_tcl" 
> target did
> not work on Linux (see above commit message), but I assume that is because you
> are still working through all the blank-in-build-tree-pathname issues for the 
> test_tcl
> target case (which tests everything to do with Tcl).
>
> 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
> __________________________ 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.    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.

   

  
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to