Hi Arjen,
>
> I think I found the cause: it was a bit hidden in directories I
> normally
> don't look at: I had a special CMake module for gfortran in
> cmake/Modules/Platform. I never committed it, apparently, but now I
> have.
That explains a lot ;)
>
> Could you check if that makes dlltool su
Hi Werner,
>
> Arjen, btw, in cygwin I have the same problem with the fortran 77
> compiler (no import library created for libplplotf77d-9.1.1.dll) when I
> add -DBUILD_TEST=ON. Can you confirm that?
>
I have solved the problem (not committed yet): I introduced a file
Cygwin-GNU-Fortran.cmake
Hi Werner,
I think I found the cause: it was a bit hidden in directories I normally
don't look at: I had a special CMake module for gfortran in
cmake/Modules/Platform. I never committed it, apparently, but now I
have.
Could you check if that makes dlltool superfluously for you? If so,
we can simp
Hi Werner,
On 2009-03-31 09:04, Werner Smekal wrote:
> Hi Arjen,
>
>>
>> I realised that something like this was going wrong by manually running
>> it with various arguments and extra print-statements.
>
> Interesting, I did the same, but there was nothing printed on the screen
> ever until I a
Hi Arjen,
> Well, I solved the problem: it turns out that Werner was on the right
> track - I needed to expand the PATH environment variable, not with
> the drivers subdirectory that contains the DLLs, but with the src
> subdirectory, as apparently "test-drv-info" links to
> "libplplot-9.6.1.dll"!
Hi Alan,
On 2009-03-30 19:44, Alan W. Irwin wrote:
>
> It's a long shot, but there was some purpose to my question. So please
> answer it with the _exact_ command (test-drv-info + argument), that was run
> by make VERBOSE=1 including the directory the command was run in.
>
> test-drv-info is
