Hi Arjen: I just learned today on the CMake list, that CMAKE_MODULE_PATH was actually interpreted as a list. Based on that information, I was able to completely reorganize our language (Ada, D, and Fortran) support files in a way that should allow us to support both CMake-2.6.x and CMake-2.8.x. The basic idea is CMAKE_MODULE_PATH is assigned different list values depending on whether the PLplot builder has CMake-2.6.x or CMake-2.8.x installed. Two of the list elements are common between CMake-2.6.x and CMake-2.8.x, but one is different.
That reorganization (revision 10805) was a rather large commit because all the changes had to be done atomically in order for PLplot builds to keep working. That commit needs a lot more testing since I have so far only made sure it worked for the default Linux build with Linux Ada, D, and gfortran compilers with shared libraries. You should look at the commit message to see the directories that are involved. The two important groups of directories from your (Fortran support) perspective are cmake/modules/language_support/cmake-2.6 cmake/modules/language_support/cmake-2.6/Platform cmake/modules/language_support/cmake-2.8 cmake/modules/language_support/cmake-2.8/Platform The former group has all your 2.6-related Fortran stuff. Please remove everything from cmake-2.6/Platform that is already supported natively by CMake-2.6.x. My guess from your discussion with Brad is you will be able to remove everything from there other than the file to support the Compaq Visual Fortran compiler for CMake-2.6.x. Please confirm that with tests on all your Windows platforms. The latter group of directories has no files at the moment. If I am interpreting the long discussion between you and Brad properly, you have a file ready to put into cmake-2.8/Platform to support the Compaq Visual Fortran compiler for CMake-2.8.x, and, of course, that will need testing by you as well. N.B. when you delete files from cmake-2.6/Platform and add a file to cmake-2.8/Platform, you will have to do the obvious corresponding maintenance of cmake/modules/language_support.cmake and examples/CMakeLists.txt. Both those CMake-related files do some processing of all the language support files so there are explicit lists of file names that have to be maintained exactly consistent with what files are present in the cmake/modules/language_support tree. I look forward to your Fortran language support commits (the deletions and the one addition I mentioned above if I have interpreted your discussions with Brad correctly) and heavy testing of those commits on various Windows platforms _both_ for CMake-2.6.x and CMake-2.8.1-RC3. Obviously, this is a fair amount of work but I hope you can do it essentially immediately. I know you prefer to work slowly and methodically, but my motivation for asking for quick results from you is I would really like to see all our Fortran support issues straightened out with thorough testing by the time CMake-2.8.1 is released, and that is going to be quite soon according to what Bill Hoffman said on the CMake list today. Of course, if your testing does find an issue with CMake-2.8.1-RC3, then Bill will probably hold the release to get the issue straightened out, but he won't know to do that unless you do your tests immediately. Of course, if you miss the CMake-2.8.1 deadline, there is always CMake-2.8.2, but then that means we have to tell our users to avoid both CMake-2.8.0 and CMake-2.8.1 for Windows Fortran, and I am sure you would prefer not to do that. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
