On 2007-03-16 21:49+0100 Werner Smekal wrote: > Hi, >> Does anybody here know the Mac OS X equivalent of the Linux LD_LIBRARY_PATH? >> (It was mentioned a year or two ago on list, but I have forgotten its name.) >> Setting that environment variable may be required before the x01a, etc., Ada >> examples will work in the build tree. >> > > DYLD_LIBRARY_PATH
Thanks, Werner, for coming through with the name of that environment variable. Setting that environment variable (to a combination of paths for the plplotadad and gnat libraries) made all the difference, and Jerry reports complete ctest success with the Ada examples now for his Mac OS X/MacAda platform. Note, Jerry already had complete success with ctest for the C examples without having to set DYLD_LIBRARY_PATH so I have no idea why it is necessary in the Ada case. I have some other priorities that are beginning to intrude in the short term at the moment, but I hope in the intermediate term to figure out some CMake build system changes so that it will no longer be necessary to use the DYLD_LIBRARY_PATH workaround to get ctest to work for MacAda. Meanwhile, it is really nice to know that workaround exists since it should allow Jerry to use the convenient ctest procedure while he figures out the thin interface anomalies we have discovered with the existing standard examples. Just to be clear, Jerry, about that convenient procedure, if all you are doing is changes in existing source code (e.g., plplotthin.adb, plplot.adb, and/or one of the examples in the source tree) but not changing configuration options or changing CMake configuration files you only have to clean out the build tree and execute cmake once, and from then on all you have to do is execute make and ctest for each source code change which should save considerable time. Also, note if you add a new example (say x02a.adb), then you have to modify examples/ada/CMakeLists.txt and test/test_ada.sh.in in an obvious way to add 02 to the lists in those files. Those files are CMake configuration files so you have to make a fresh start (clean out the build tree, run cmake) after such a change. However, while debugging the new example afterward with just source code changes, you can stick with just the make and ctest commands. I hope those important distinctions between changes to source code and changes to CMake configuration files are clear. 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 Yorick front-end to PLplot (yplot.sf.net); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
