Hi Troy, The flag -p, +P, -P are documented in the CINT documentation. The simpliest way is to just type cint -help (or see the web pages) To get more information from cint (rootcint) you can add -v (or for even more information -t) __after__ the -c Cheers, Philippe. -----Original Message----- From: owner-roottalk@pcroot.cern.ch [mailto:owner-roottalk@pcroot.cern.ch]On Behalf Of Troy Straszheim Sent: Saturday, February 07, 2004 6:10 AM To: roottalk@pcroot.cern.ch Subject: [ROOT] rootcint -p +P -P Hi rooters -- I asked a little while ago about the preprocessor arguments to "rootcint" and got a quick answer: -p, after the -c, turns on use of the compiler's preprocessor. I notice completely different behavior between -p +P and -P and cannot find any documentation. With the +P I get this behavior: rootcint -v -f RootDict.cxx -c +P Classes.h LinkDef.h /tmp/Tq5OS2_cint.cxx:1:37: -I/usr/local/root/include: No such file or directory /tmp/DvjBKN_cint.cxx:1:33: -I/usr/local/root/src: No such file or directory and many more preprocessor flags With -P I get this: rootcint -v -f RootDict.cxx -c -P Classes.h LinkDef.h Error: cannot open file "TROOT.h" FILE: LINE:0 So, it would be nice to know exactly what each is doing... Also it would be nice to know if there is a way to get rootcint to show me more of what it is doing than -v4 reveals. Thanks, Troy Straszheim
This archive was generated by hypermail 2b29 : Sun Jan 02 2005 - 05:50:05 MET