Alan W. Irwin wrote: > On 2008-10-06 09:29+0200 Arjen Markus wrote: > >> Alan W. Irwin wrote: >> >>> On 2008-10-02 22:04+0200 Arjen Markus wrote: >>> >>> >>>> Hello, >>>> >>>> I am picking up the issue of gfortran 4.3.2 under MinGW again. >>>> I have modified the source code (the import/export stuff) so >>>> that the libraries are created appropriately, but while >>>> building the examples, I run into the problem that the file >>>> "libplplotf77d.dll.a" is not found (there is a file >>>> "libplplotf77cd.dll.a" >>>> for the C-Fortran interfacing). >>>> >>>> I will check this problem, but may need some advice. >>>> >>> >>> We need a lot more information before we can efficiently help you. >>> >> Well, the cause of the problem is clear now: when linking the Fortran >> bindings >> into a DLL, gfortran would need the option -Wl,-out-implib,... (or >> something >> similar) to produce the missing library. >> >> This option _is_ present in the gcc part to create the DLL >> libplplotf77cd.dll. >> >> I checked to see if I could easily add it, but I have not found a >> specific CMake >> module for gfortran under Windows. >> >> So my question now is: Should I go ahead and add such module for this >> particular >> combination (as part of general modules) or add it to the >> CMakeLists.txt file as >> a special case. Or is there another way I should proceed? > > > Hi Arjen: > > Assuming I understand the naming conventions properly, I think you > just need > another Platform file called Windows-GNU-Fortran.cmake with the > appropriate > gfortran flags corresponding to the equivalent C flags in > Windows-gcc.cmake. > The location for that file for some time to come should be > cmake/modules/Platform. Once you are happy with all the Fortran > compiler and > linking flags on MinGW, you will probably want to submit that file to the > CMake project to help others. Also in the distant future when our > minimum > CMake version corresponds to the version of CMake that includes that > Platform file, we can drop that file from PLplot. > > Here is how I came up with the above name. Currently on Linux the > gfortran > compiler and link flags are handled by Linux-GNU-Fortran.cmake. > Currently, > on Windows (MinGW) the gcc compiler and link flags are handled by > Windows-gcc.cmake. Combine the two and you get the name > Windows-GNU-Fortran.cmake. If that is right, you will see all the > flags set > there actually used for compilation and linking on MinGW with the > gfortran > compiler, but if that name is wrong the file will have no effect, and you > may have to experiment a little bit to get the correct name. > > Hope this advice helps to point you in the right direction. > Hi Alan,
I think you are correct in that - I will try to solve the issue this way (better than messing up the logic in the Fortran bindings file) Regards, Arjen ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
