On 2014-01-06 20:38-0700 Orion Poplawski wrote:
> On 01/03/2014 05:59 PM, Alan W. Irwin wrote:
>> For the PLplot build system it should be straightforward to create an
>> Octave version test. Also, I am pretty sure that swig users are
>> allowed to redefine any core swig functionality. Thus, for
On 01/03/2014 05:59 PM, Alan W. Irwin wrote:
> On 2014-01-03 15:07-0700 Orion Poplawski wrote:
>
>> On 12/31/2013 06:50 PM, Alan W. Irwin wrote:
>>> Hi Orion:
>>>
>>> Thanks for doing that suggested experiment. More below
>>> in context.
>>>
>>> On 2013-12-31 16:52-0700 Orion Poplawski wrote:
>>>
On 2014-01-03 15:07-0700 Orion Poplawski wrote:
> On 12/31/2013 06:50 PM, Alan W. Irwin wrote:
>> Hi Orion:
>>
>> Thanks for doing that suggested experiment. More below
>> in context.
>>
>> On 2013-12-31 16:52-0700 Orion Poplawski wrote:
>>
>>> On 12/31/2013 11:56 AM, Alan W. Irwin wrote:
On
On 12/31/2013 06:50 PM, Alan W. Irwin wrote:
> Hi Orion:
>
> Thanks for doing that suggested experiment. More below
> in context.
>
> On 2013-12-31 16:52-0700 Orion Poplawski wrote:
>
>> On 12/31/2013 11:56 AM, Alan W. Irwin wrote:
>>> On 2013-12-30 13:42-0700 Orion Poplawski wrote:
>>>
Ah
Hi Orion:
Thanks for doing that suggested experiment. More below
in context.
On 2013-12-31 16:52-0700 Orion Poplawski wrote:
> On 12/31/2013 11:56 AM, Alan W. Irwin wrote:
>> On 2013-12-30 13:42-0700 Orion Poplawski wrote:
>>
>>> Ah, you hit the nail on the head - they dropped OCTAVE_API_VERSIO
On 12/31/2013 11:56 AM, Alan W. Irwin wrote:
> On 2013-12-30 13:42-0700 Orion Poplawski wrote:
>
>> Ah, you hit the nail on the head - they dropped OCTAVE_API_VERSION_NUMBER
>> completely. I've sent an email to the octave developers asking why.
>
> To see if there are any more octave-3.8.0 issue
On 2013-12-30 13:42-0700 Orion Poplawski wrote:
> Ah, you hit the nail on the head - they dropped OCTAVE_API_VERSION_NUMBER
> completely. I've sent an email to the octave developers asking why.
To see if there are any more octave-3.8.0 issues beyond this one, I
suggest you temporarily add
#defi
On 12/30/2013 01:08 PM, Alan W. Irwin wrote:
> On 2013-12-29 20:39-0700 Orion Poplawski wrote:
>
>> On 12/29/2013 08:25 PM, Orion Poplawski wrote:
>>> On 12/29/2013 01:34 PM, Alan W. Irwin wrote:
Please let me know if my latest PLplot change from config.h to
plplot_config.h (revision 129
On 2013-12-30 12:08-0800 Alan W. Irwin wrote:
> Note my incoming e-mail has been disrupted again today by my
> University service provider so if you or Andrew have already come to
> similar conclusions, I haven't had a chance to see them yet.
P.S. Actually, I jumped to a premature conclusion abo
On 2013-12-29 20:39-0700 Orion Poplawski wrote:
> On 12/29/2013 08:25 PM, Orion Poplawski wrote:
>> On 12/29/2013 01:34 PM, Alan W. Irwin wrote:
>>> Please let me know if my latest PLplot change from config.h to
>>> plplot_config.h (revision 12914) solves this issue. Of course, if it
>>> doesn't s
On 12/29/2013 08:25 PM, Orion Poplawski wrote:
> On 12/29/2013 01:34 PM, Alan W. Irwin wrote:
>> Please let me know if my latest PLplot change from config.h to
>> plplot_config.h (revision 12914) solves this issue. Of course, if it
>> doesn't solve it, the change was worth doing anyway. And if it d
On 12/29/2013 01:34 PM, Alan W. Irwin wrote:
> Please let me know if my latest PLplot change from config.h to
> plplot_config.h (revision 12914) solves this issue. Of course, if it
> doesn't solve it, the change was worth doing anyway. And if it does
> solve it, I hope your bug report still convinc
On 2013-12-29 11:18-0700 Orion Poplawski wrote:
> On 12/29/2013 11:00 AM, Alan W. Irwin wrote:
>> [...T]he root cause is a subtle change in how
>> octave attempts to include its config.h. For 3.6.x, oct.h used
>>
>> #include "config.h"
>>
>> which meant that file (located in the same directory as
On 12/29/2013 11:00 AM, Alan W. Irwin wrote:
> On 2013-12-29 08:41-0700 Orion Poplawski wrote:
>
>> On 12/28/2013 10:49 PM, Alan W. Irwin wrote:
>>> On 2013-12-28 16:53-0700 Orion Poplawski wrote:
>>>
On 06/27/2013 11:44 AM, RCY wrote:
> Hi,
> I am trying to build the development ve
On 2013-12-29 08:41-0700 Orion Poplawski wrote:
> On 12/28/2013 10:49 PM, Alan W. Irwin wrote:
>> On 2013-12-28 16:53-0700 Orion Poplawski wrote:
>>
>>> On 06/27/2013 11:44 AM, RCY wrote:
Hi,
I am trying to build the development version of plplot with octave
bindings. However I ge
On 12/28/2013 10:49 PM, Alan W. Irwin wrote:
> On 2013-12-28 16:53-0700 Orion Poplawski wrote:
>
>> On 06/27/2013 11:44 AM, RCY wrote:
>>> Hi,
>>> I am trying to build the development version of plplot with octave
>>> bindings. However I get numerous errors.
>>> Is the version incompatible with
On 2013-12-28 16:53-0700 Orion Poplawski wrote:
> On 06/27/2013 11:44 AM, RCY wrote:
>> Hi,
>> I am trying to build the development version of plplot with octave
>> bindings. However I get numerous errors.
>> Is the version incompatible with later versions of octave?
>>
>> Thanks
>>
>> [ 71%] Bu
On 06/27/2013 11:44 AM, RCY wrote:
> Hi,
> I am trying to build the development version of plplot with octave
> bindings. However I get numerous errors.
> Is the version incompatible with later versions of octave?
>
> Thanks
>
> [ 71%] Building CXX object
> bindings/octave/CMakeFiles/plplot_octav
Hi Arjen and Alan
Arjen - to create a 64 bt build add Win64 to the generator, e.g. -G "Visual
Studio 11 Win64". Which made me think a moment - if it's the generator which
defines the project then why do we need to use the 64 bit VC++ Tools command
prompt? In fact maybe CMAKE sees the 64 bit comp
Hi Alan
Unfortunately it's still not completing. CMAKE output below
D:\SourceCode\Libraries\plplotinstall>set CXXFLAGS=/DUNICODE /D_UNICODE
D:\SourceCode\Libraries\plplotinstall>set CFLAGS=/DUNICODE /D_UNICODE
D:\SourceCode\Libraries\plplotinstall>cd "D:/SourceCode/Libraries/plplot_trunk_s
t
On 2013-12-12 13:13-0800 phil rosenberg wrote:
> Hi Andrew and Alan
> Unfortunately I'm not sure either problem is fixed. So here is my
output with fortran enabled
Hi Phil"
It looks to me that the Fortran build system logic is working
correctly on your platform. The soft landing for that (a
On 2013-12-12 19:53- Andrew Ross wrote:
> On Thursday 12 Dec 2013 11:09:28 Alan W. Irwin wrote:
>> On 2013-12-12 09:44-0800 Alan W. Irwin wrote:
>>> On 2013-12-12 06:06-0800 phil rosenberg wrote:
I've tried to hunt down the actual revisions where the problems
>>>
>>> occurred. After a cou
On Thursday 12 Dec 2013 11:09:28 Alan W. Irwin wrote:
> On 2013-12-12 09:44-0800 Alan W. Irwin wrote:
> > On 2013-12-12 06:06-0800 phil rosenberg wrote:
> >> I've tried to hunt down the actual revisions where the problems
> >
> > occurred. After a couple of hiccups with Tortoise SVN I've found tha
On 2013-12-12 09:44-0800 Alan W. Irwin wrote:
> On 2013-12-12 06:06-0800 phil rosenberg wrote:
>
>> I've tried to hunt down the actual revisions where the problems
> occurred. After a couple of hiccups with Tortoise SVN I've found that
> revision 12725 was the first where I encounter problems with
On 2013-12-12 06:06-0800 phil rosenberg wrote:
> I've tried to hunt down the actual revisions where the problems
occurred. After a couple of hiccups with Tortoise SVN I've found that
revision 12725 was the first where I encounter problems with the
Fortran binding not being automatically disabled a
). I think Andrew is right in attributing this issue to
the recent retirement of F77.
Regards,
Arjen
From:phil rosenberg [mailto:[email protected]]
Sent: Thursday, December 12, 2013 11:13 AM
To: [email protected]
Subject: Re: [Plplot-devel] Build problems on
this issue to
the recent retirement of F77.
Regards,
Arjen
From: phil rosenberg [mailto:[email protected]]
Sent: Thursday, December 12, 2013 11:13 AM
To: [email protected]
Subject: Re: [Plplot-devel] Build problems on Windows
Sorry I spoke too soon, although revision
Hi Andrew
Yes a completely clean build tree. I'm now on Win8 running VS2012, but as I
just emailed, going back 100 revisions allows CMAKE to complete.
On Thursday, 12 December 2013, 9:56, Andrew Ross
wrote:
Hi Phil,
I'll leave Alan to comment on the QT changes since this was his patch.
T
Sorry I spoke too soon, although revision 12848 reaches the end of the build
cycle it doesn't actually create the visual studio project, instead giving a
Configuration incomplete - errors occurred! message. The only error I can see
in the output is
CMake Error at cmake/modules/plplot_functio
On 2009-02-27 21:54+0100 Werner Smekal wrote:
> Hi Thomas,
>> By any chance is a cross compile from linux to win32 or win64 supported?
>> Just for C that is. I'm all thumbs with cmake. If this has not been done
>> before, I'll be glad to test it, if someone can give me some clue how to
>> start
Hi Thomas,
> By any chance is a cross compile from linux to win32 or win64 supported?
> Just for C that is. I'm all thumbs with cmake. If this has not been done
> before, I'll be glad to test it, if someone can give me some clue how to
> start. For instance I have a home built cross mingw tool c
Just to follow up. I did get it to build by not trying to take
everything out except extcairo. Thanks a ton for the reply.
By any chance is a cross compile from linux to win32 or win64 supported?
Just for C that is. I'm all thumbs with cmake. If this has not been done
before, I'll be glad to te
On 2009-02-25 18:22-0600 Thomas Stover wrote:
> Hi, I just signed up to the list, so my apologies if my post is
> completely out of whack.
>
> -Firstly the documentation (wiki & INSTALL) use a file named
> plplot_cmake. This file is not present in either 5.9.2 source tree nor
> the current svn tru
33 matches
Mail list logo
