bomben
January 28, 2016, 4:18pm
1
Dear all,
I managed to solve the following problem:
[quote]
Error in : The file IV.C can not be found in the include path:[/quote]
by adding in my script:
gSystem->AddIncludePath("-I/Users/mbomben/work/root_macros");
The code of the script looks like this:
{
gROOT->Reset();
gSystem->AddIncludePath("-I/Users/mbomben/work/root_macros");
gSystem->CompileMacro("IV.C");
gSystem->Load("IV_C.so");
double alpha;
IV("/Users/bomben/work/RD50/Natascha/newPetaseccaLow/ninp_fei4_3pixels_fluence\=2e+15_bias\=2000_RD50_PX2_Current_pruned.dat","SIMU",50e-8,200e-4,130,253.15,2e15,alpha);
}
My questions is the following: is it possible to add permanently (via .rootrc?) that directory to my root installation, please? Or have I to add it to the path every time a create a new script that wants to use that library?
Many thanks in advance and best regards,
Marco Bomben
Danilo
January 28, 2016, 6:51pm
2
Hi marco,
You could set up a “rootlogon” script. See e.g. Step by step rootlogon.C
Cheers,
Danilo
pcanal
January 28, 2016, 9:21pm
3
Hi Marco,
You also create a .rootrc in your home directory containing[code]# Path used to find macros.
Paths are different for Unix and Windows. The example shows the defaults
for all ROOT applications for either Unix or Windows.
Unix..Root.MacroPath: .:$(ROOTSYS)/macros:/var/tmp/mm
WinNT. .Root.MacroPath: .;$(ROOTSYS)/macros;/Users/mbomben/work/root_macros
[/code]and use (instead of calling CompileMacro directly)gROOT->LoadMacro("IV.C+");
Cheers,
Philippe.
Philippe, I think he (also?) wants: # Add additional include directives for ACLiC compilations.
#ACLiC.IncludePaths: -I/where/the/includes/are
bomben
January 30, 2016, 2:53pm
6
Thank you all!
Fixing ACLiC.IncludePaths did the magic.
Thanks again and best regards,
Marco Bomben