On 2015-04-05 01:17-0700 Alan W. Irwin wrote:
> On 2015-04-04 23:11-0700 Greg Jung wrote:
>
>> afaict these environment variables are essential for plots:
>>
>> PLPLOT_DRV_DIR=/usr/local/lib/plplot5.10.0/drivers
>> PLPLOT_HOME=/usr/local/share/plplot5.10.0/
>>
>> DRV_DIR for dynamic loading, to ge
On 2015-04-04 23:11-0700 Greg Jung wrote:
> afaict these environment variables are essential for plots:
>
> PLPLOT_DRV_DIR=/usr/local/lib/plplot5.10.0/drivers
> PLPLOT_HOME=/usr/local/share/plplot5.10.0/
>
> DRV_DIR for dynamic loading, to get the driver_info files (.dll files
> are to be pick
> u
afaict these environment variables are essential for plots:
PLPLOT_DRV_DIR=/usr/local/lib/plplot5.10.0/drivers
PLPLOT_HOME=/usr/local/share/plplot5.10.0/
DRV_DIR for dynamic loading, to get the driver_info files (.dll files
are to be pick
up in PATH) and PLPLOT_HOME for support files:
greg@Homerw
On 2015-04-04 21:27- Arjen Markus wrote:
> I had to suppress the test_interactive part as well as the traditional build,
> but then it finished all right. See the attached tgz-file for the details.
I agree that limited Cygwin result looks good (other than the
test_interactive and traditional
On 2015-04-04 19:34- Arjen Markus wrote:
> Hi Alan,
>
>
>
>> -Original Message-
>> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>> Sent: Saturday, April 04, 2015 9:04 PM
>> To: Arjen Markus
>> Cc: Greg Jung; Phil Rosenberg; Jim Dishaw; PLplot development list
>> Subject: RE:
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Saturday, April 04, 2015 9:04 PM
> To: Arjen Markus
> Cc: Greg Jung; Phil Rosenberg; Jim Dishaw; PLplot development list
> Subject: RE: Release status: call for comprehensive testing: Cygwin
>
On 2015-04-04 15:31- Arjen Markus wrote:
> Hi Alan,
>
>
>
>> -Original Message-
>> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>>
>> @Arjen, Phil, and Jim:
>>
>> As release manager, that latter possibility of a regression in comprehensive
>> testing
>> on the Cygwin platfo
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>
> @Arjen, Phil, and Jim:
>
> As release manager, that latter possibility of a regression in comprehensive
> testing
> on the Cygwin platform really concerns me, and I ask at least one of you guys
Hi Alan, Greg,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>
> @Greg: You have much more experience with Cygwin than I do (since my actual
> experience is zero). Nevertheless, historically there has been lots of
> warnings on
> the CMake list that Cygw
On 2015-04-03 14:06-0700 Greg Jung wrote:
> In Cygwin, I do use the cygwin cmake; but it isn't distributed by
> cygwin, I built it from source. At one point I tried the windows
> cmake from cygwin and it failed miserably.
@Greg:
Thanks for that clarification. I agree that cmake built on Cygwin
In Cygwin, I do use the cygwin cmake; but it isn't distributed by
cygwin, I built it from source. At one point I tried the windows
cmake from cygwin and it failed miserably.
On Fri, Apr 3, 2015 at 12:20 PM, Alan W. Irwin
wrote:
> On 2015-04-02 22:57-0700 Greg Jung wrote:
>
>> This is a long-stan
On 2015-04-02 22:57-0700 Greg Jung wrote:
> This is a long-standing cygwin warning, "CMake no longer defines WIN32
> on Cygwin!"
> for those rip-van-winkles coming back to cygwin and somehow wanting
> WIN32 to be defined.
> I am very familar with the possible quirks that can arise with Cmake;
> if
12 matches
Mail list logo
