On Fri, May 08, 2009 at 09:38:45AM +0200, Arjen Markus wrote: > On 2009-05-05 09:47, Werner Smekal wrote: > > Hi Arjen, > >> > >> I do not know whether I will be able to solve the Fortran issue on > >> Windows before this weekend - it would involve building static AND > >> dynamic libraries at the same time. I do not quite know how to do > >> that. > > > > why that? As long as the names are not the same (which is the case for > > cygwin I think, but not for bare windows), you could just use > > > > add_library( f77shared SHARED ...) > > add_library( f77static STATIC ...) > > > > I think you still need to name the targets different, but then set the > > output name to the expected one with: > > > > set_target_properties( f77static PROPERTIES OUTPUT_NAME f77correct > > CLEAN_DIRECT_OUTPUT 1) > > > > the CLEAN_DIRECT_OUTPUT 1 is also needed, look here: > > > > http://www.mail-archive.com/cm...@cmake.org/msg04743.html > > http://www.mail-archive.com/cm...@cmake.org/msg04746.html > > > > Hi Werner, > > I have been able to implement the correct logic for this issue. > Here are a few notes: > > - If you build with dynamic libraries on Windows using Cygwin, MinGW or > MSYS, then an additional _static_ library is made, which contains > the plparseopts routine. This ensures that the Fortran run-time > library correctly passes all the arguments. > > - I made changes in several files to ensure that this works properly - > the check for the functionality of command-line arguments is now > done for both FORTRAN 77 and Fortran 95. > > - In the post-release phase I intend to change the test to a more > "semantic" one, but that is more involved than I had time for now. > > Separate issues regarding the present state: > > - I have a problem with example x20f for Fortran 95 with one single > compiler (the "tdm" release of gfortran under MinGW). It fails to > read the temporary file created for the header of the picture file. > Really odd. (The F77 version works fine with that same compiler) > > - If I do not set the path to include my winbash installation, the > build sometimes fails at the point where pkgIndex.tcl is handled > (only MinGW). Not sure how - I have not been able to trace the error > in the makefiles yet (the error message is non-informative) > > - Testing the Tcl examples remains an issue - I need to set TCL_LIBRARY > before running the tests. Something to look into after 5.9.4. > > - Tk is recognised under Cygwin, but the build fails because of a > few UNIX/Linux-specific functions that are not available under Cygwin.
The tk code is currently written in a unix-specific manner. The tk driver makes use of fifo pipes / sockets to communicate which may not be available on other platforms? Also the plframe code in bindings/tk uses the xwin driver, so as is it probably won't work on windows. This has not been widely used or supported in recent years so no-one has ever tried to make it (or at least parts of it) compatible with other operating systems. Perhaps it would be better to disable the tk code in cmake unless you are on a unix platform? Andrew ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
