>> Hi Alan, > > Could you please revert the change for now and do it after the > release? I > think your implementation will not introduce any nasty build-system > bugs, > but my instinct says we should have a longer testing period to make > sure.
Sure, done. > > > Also, I think we need some additional discussion here of whether it is > worthwhile to have a variety of LIB_TAG's. That does give us > different name > spaces for library names and device drivers so they can all coexist > happily > under the same installation prefix, but other components of the PLplot > install will just get overwritten by each install with a separate > LIB_TAG. I > think Maurice is the only one that has practical experience with > installs to > the same prefix of single and double-precision versions of PLplot, > but I am > not sure whether he is still doing that or how extensive his testing > has > been of that situation. I actually didn't mean that different versions of plplot (with different names) should be installed into the same directories. They should stay in different directories but have different library names. > > > Of course, another completely safe alternative to changing LIB_TAG > is simply > to use differently named install prefixes for each different version > of > PLplot that you configure. That's a possibility though but doesn't work on Windows. I could have a debug and release version of plplot in different installation directories, true. But all .lib files and .dll files are the same. So even if I set the path to both bin directories (where the dlls are), it will choose the first dll it finds - which is in one of the cases the wrong one. I would need to change the PATH variable everytime I change from build to debug release or vice versa. That's not very convenient in Windows (Start->System Preferences->System->Another menu- >Environment Variables, change variable, click two times ok and close the system preferences). Restart Visual C++. Might not work, since Visual C++ somehow caches the enviroment variables sometimes, so I have to REBOOT! (Windows is funny, isn't it :). I know, that in Linux it's not a problem, and I use different versions of plplot in different install directories already, but even here - I could set the LD_LIBRARY_PATH to both or all install directories and I wouldn't need to reset them or start a new terminal (this is now what I do e.g. for the several wxwidgets installations). So, I don't propose that changing the library name should be common use, but there are cases, where I believe that this is the only convenient way to work with several versions of the library and the configuration should provide a way to enable this. What do you think? Regards, Werner > > > 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 > __________________________ -- Dr. Werner Smekal Institut fuer Allgemeine Physik Technische Universitaet Wien Wiedner Hauptstr 8-10 A-1040 Wien Austria email: [EMAIL PROTECTED] web: http://www.iap.tuwien.ac.at/~smekal phone: +43-(0)1-58801-13463 (office), +43-(0)1-58801-13469 (laboratory) fax: +43-(0)1-58801-13499 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
