RE: [ROOT] Problems with #include "path/file.h" in CINT script.

From: Philippe Canal (pcanal@fnal.gov)
Date: Wed Jul 18 2001 - 15:50:46 MEST 

Hi Brett,

MacroPath does not have a bug making it fails if '.' is
the first directory.  Try 

root [0] gROOT->SetMacroPath("$MYPATH:.")

Cheers,

Philippe.


-----Original Message-----
From: Brett Viren [mailto:bviren@minos.phy.bnl.gov]On Behalf Of Brett
Viren
Sent: Tuesday, July 17, 2001 5:49 PM
To: Philippe Canal
Cc: roottalk@pcroot.cern.ch
Subject: RE: [ROOT] Problems with #include "path/file.h" in CINT script.


Hi Philippe,

Philippe Canal writes:

 > Looking at your example, it is seems to exhibit the expected behavior.

I think you missed the lines with "MYPATH".  Sorry not to make it more
clear.  Here are the important lines again:

bash> cd /full/path/to/somepath
bash> cd ..
bash> export MYPATH=`pwd`
bash> cd somepath
...
root [0] gROOT->SetMacroPath(".:$MYPATH")
root [1] .x A.C
Error: cannot open file "somepath/A.h"  FILE:A.C LINE:2
*** Interpreter error recovered ***

So, "somepath/A.h" should, I assumed, be found because "/full/path/to"
is given to the include search path.

I also tried adding the path with the ".includes" command and
"gSystem->SetIncludePath()" and it still fails to find A.h

BTW, with ACLiC, ie, ".x A.C++" things work as expected.

Thanks,
-Brett.

This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:52 MET