I think I have tracked down the problem with macro search paths which I reported earlier. In my example, I was trying to find dir1/dir2/macro.C using the relative path dir2/macro.C and with dir1/ in my macro search path. This does not appear to work, ie, it looks like the search path is only applied to bare filenames. Is this a bug or a feature? I can understand why the search path should not be applied to an absolute path, but why shouldn't it be tried for relative paths? cheers, David On Tue, 30 Nov 1999, David Kirkby wrote: > Hello - I am having trouble loading a macro in my search path. I have > tested the following with 2.23/09: > > root [0] .L RooFitTools/RooFitTest.cc > Error in <TRint::ProcessLine>: macro RooFitTools/RooFitTest.cc not found in path .. > root [1] .L ../RooFitTools/RooFitTest.cc > > > My .rootrc contains the single line: > > Root.MacroPath: .. > > Any ideas? It looks like RInt knows about my path since it correctly > prints it in the error message. Command completion does list this file > via the search path, and adding the '..' by hand also works. > > David
This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:16 MET