Hi Alan,
With the latest version the warnings are indeed gone:
-- CMake version = 3.1.2
-- CMAKE_SYSTEM_NAME = CYGWIN
-- SH_EXECUTABLE = /usr/bin/bash.exe
-- Checking whether system has ANSI C header files
-- ANSI C header files - found
-- SWIG_VERSION = 2.0.12
-- WARNING: Perl module XML
Hi Alan, James,
I am not entirely sure that it is possible to eliminate all intermediate C
code, for instance because of storing pointers to callback functions and NULL
arguments, but using the iso_c_binding features it will at the very least be
possible to let the linker detect missing inter
On 2015-05-13 07:27- Arjen Markus wrote:
> Hi Alan,
>
>
>
> Please find the result of the comprehensive test in the attachment. From a
> quick inspection of the report I see that there are various issues:
>
> -The Fortran examples are not properly built because of the name of
> the l
If I understand correctly, then this is pretty much what we do in
gtk-fortran where a script is able to parse the gtk+ (along with gdk, glib,
cairo and the other dependencies) headers to make a set of Fortran
interface definitions.
There are only a couple of significant issues that need to be cons
On 2015-05-17 07:38- Arjen Markus wrote:
> My new bindings would not have prevented this [argument kind error], as it
> was an omission, not an incorrect implementation.
Hi Arjen:
This is an important point that I think needs more discussion because
the new Fortran binding for ephcom very m
Hi Orion:
In the last month or so you brought a number of linking issues for
the traditional build system to my attention. I believe
commit id = 6a5bad5 should fix those.
Would you please run your traditional build tests on Fedora again to
check that?
Once you confirm all is well (i.e., no over
Hi Alan,
> -Original Message-
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> > Ah, that is clear: there is no interface definition for plctime. So
> the compiler was using the traditional F77 rules and could not check the
> correctness
> of the types. I will fix this.
>
>
