On Thu, Aug 14, 2008 at 08:14:25AM -0600, [EMAIL PROTECTED] wrote: > > > Doing gdb sessions in the build tree is pretty tricky because of all the > > setup (e.g., setting environment variables) you have to do first. So I > > don't > > recommend it except for rare emergencies where you get errors in the build > > tree but not the install tree. Furthermore, ctest doesn't have a facility > > to > > pass options on to plplot-test.sh so we have to choose the plplot-test.sh > > options for the build tree at cmake time which would not be very > > convenient > > for you. > > > > So for the above reasons I am not completely keen on your idea. However, > > if > > you still are keen after considering what I have said above, then please > > send me a patch with the implementation (not only the changes to > > plplot-test.sh.in, but the extra logic required in the various > > test_*.sh.in > > files). Assuming the patch looks okay, I can deal with the cmake details > > so > > that there is a cmake option such that ctest runs plplot-test.sh with both > > the --verbose and --debug options. > > My problem is that I'm building RPM packages and so it's pretty much > impossible to do the testing in the install tree. I'll work on a patch.
It is really not that hard to work in the build tree. All you usually need to set is PLPLOT_LIB to point to the data directory in the source tree. Andrew ------------------------------------------------------------------------- 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
