Hi Alan, James,
In the attachment you will find a demonstration of the sort of Fortran bindings
I have in mind. The essence is:
-Use iso_c_binding to call the C functions directly (no intervening C
wrapper if that can be avoided)
-Use the renaming feature of the use statement
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>
> The first error message for the case of the traditional build of the f95
> examples when
> PLplot was statically built was as follows:
>
> /cygdrive/d/plplot-
> svn/comprehensive_test_disposeable
On 2015-05-21 08:07- Arjen Markus wrote:
> Hi Alan,
>
>
>
>> -Original Message-
>> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>
>>
>> The first error message for the case of the traditional build of the f95
>> examples when
>> PLplot was statically built was as follows:
>>
On 2015-05-21 07:53- Arjen Markus wrote:
> Hi Alan, James,
>
>
>
> In the attachment you will find a demonstration of the sort of Fortran
> bindings I have in mind. The essence is:
>
> -Use iso_c_binding to call the C functions directly (no intervening C
> wrapper if that can be avoi
On 2015-05-18 00:57-0700 Alan W. Irwin wrote:
> On 2015-05-18 06:56- Arjen Markus wrote:
>
>> Hi Alan,
>>
>>
>>
>> With the latest version the [Cygwin] warnings are indeed gone:
>
> Hi Arjen:
>
> It was good to hear that issue (and other more subtle/dangerous
> issues for which that spurious w
Hi Alan and Ben
Yes, with the new system in place a new wxPNG driver would be as
simple as passing in a memoryDC then a function call to write it to
file as any number of raster formats. It was on my list before the
last release, but I never quite found the time. It is still on the
list though for
Hello Laurent
My apologies for not responding sooner. I have unfortunately not been
able to spend time on PLplot recently, but am now getting back to
things. I will look into the memory leaks you described as soon as I
can.
Phil
On 21 April 2015 at 21:42, laurent Berger wrote:
> Hi,
>
> I look f
Alan,
I think your summary is probably correct, but the solution of just
explicitly linking stdc++ is so simple, that it makes me think it must be
possible to work round this. A flag if there is any C++ code would be
sufficient to identify the need to link with stdc++?
Andrew
On Wed, May 20, 20
Hi Orion
Thanks for the report. I will look at it asap.
Phil
On 24 April 2015 at 23:05, Orion Poplawski wrote:
> I should not that these are with the installed examples:
>
> /usr/bin/c++ wxPLplotDemo.cpp -o wxPLplotDemo -D_FILE_OFFSET_BITS=64
> -D_LARGE_FILES -D__WXGTK__ -I/usr/include/plplot
I should probably add that this would for g++, but perhaps not other
compilers. This is a common enough case that it is perhaps worth
supporting as a special case nontheless?
Or we could take the decision that cmake builds are the way to go, and we
can't support all non-standard cases for the tr
Indeed for the wxWidgets driver it is bad too. When I first started
using PLplot I spent a lot of time wondering why my wxWidgets apps
kept "crashing" It turned out to be mostly due to plplot exit calls
when e.g. the Hershey font files weren't found.
Also for thread safety we are likely going to h
Oh and floating point coordinate system was on there too.
Phil
On 21 May 2015 at 23:07, Phil Rosenberg wrote:
> Indeed for the wxWidgets driver it is bad too. When I first started
> using PLplot I spent a lot of time wondering why my wxWidgets apps
> kept "crashing" It turned out to be mostly du
Hi Jim, Alan et al
Some (rather late) input into all this. GDI is the oldest windows
rendering API in use. Its major disadvantage is that it does not
support antialiasing so the out put is not very good, however it does
support hardware acceleration. GDI+ was the successor. It gives you
antialiasi
Hi Alan
I just did a git pull and tried to build PLPlot this evening and got a
massive number of build errors.
Some are related to 64 bit/32 bit conflicts which I have had problems
with in the past and can't remember how I resolved them.
Another one is below
7> Building Custom Rule D:/usr/local/
Please send me the errors. I'm getting a windows build machine going, so I will
take a look at that c
> On May 21, 2015, at 6:51 PM, Phil Rosenberg wrote:
>
> Hi Alan
> I just did a git pull and tried to build PLPlot this evening and got a
> massive number of build errors.
>
> Some are relat
On 2015-05-21 09:18- Arjen Markus wrote:
> The comprehensive test has finished on Cygwin without any
complaints. I have not checked the report extensively but it looks as
if all went well - no deviations reported. The details are in the
attachment.
Hi Arjen:
My detailed look showed everythin
On 2015-05-21 22:58+0100 Phil Rosenberg wrote:
> Hi Orion
> Thanks for the report. I will look at it asap.
Hi Phil:
Note, I have fixed the actual error that Orion noted at the end of his
message by my recent reform of the entire traditional build system.
However, that change did not address the
Hi Andrew:
I will respond to your two posts here.
On 2015-05-21 22:54+0100 Andrew Ross wrote:
>
> Alan,
>
> I think your summary is probably correct
Good. That is a big relief to me that I wasn't missing
anything obvious, and thanks for that review.
> [B]ut the solution of just
> explicitly li
> On May 14, 2015, at 12:11 AM, Alan W. Irwin wrote:
>
> On 2015-05-13 21:44-0500 Aaron Hexamer wrote:
>
>> Would it be developed using the GDI? If so, then maybe wingdi?
>
> Hi Aaron:
>
> To respond to your first question even though I am not
> that familiar with Windows, I did look up the
On 2015-05-21 23:39+0100 Phil Rosenberg wrote:
> Regarding text, uniscribe has as noted earlier been superseded by
> directText, but I don't know how far back such compatibility goes. I
> do have some code that I once wrote intending to push into PLplot (but
> again never finished) that took unisc
On 2015-05-21 23:51+0100 Phil Rosenberg wrote:
> This [error when building this app] seems odd because I don't think
> plhershey-unicode-gen.exe is
> built on Windows. Has something changed here?
Hi Phil:
That executable is always built for the Linux case, and I
can also answer this question fo
Hi Lewis:
On 2015-05-21 17:51-0500 J. Lewis Muir wrote:
> On 5/18/15 5:01 PM, Alan W. Irwin wrote:
>> So could you give the latest version of our git master branch
>> (which will soon form the basis for the forthcoming 5.11.1
>> release) a try to see if that solves the above issue? If so I
>> wi
Hi Lewis:
I am going to use a new subject line for this question for obvious
reasons.
On 2015-05-21 17:51-0500 J. Lewis Muir wrote:
> P.S. Even though the problem I reported appears to have been fixed,
> my build did not succeed, so I'm guessing I hit a new issue. The
> build failed as indicate
On 2015-05-21 22:14-0400 Jim Dishaw wrote:
> Bad news. I searched for my old Windows driver and I have lost it
to the ether. I found some remnants, but not enough to compile. I
can a recreate it without too much difficultly. The driver version
that I had created was a merge between the X11 and
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
>
> My detailed look showed everything was fine for the limited number of PLplot
> components tested other than the remaining issue with the "CMake no longer
> defines WIN32 on Cygwin!" warning which _
25 matches
Mail list logo
