Opened 8 years ago
Last modified 8 years ago
#1017 new Enhancement
Update Makefile for use as CMSSW External Package — at Version 2
Reported by: | Alexx Perloff | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Delphes code | Version: | Delphes 3 |
Keywords: | Makefile, CMSSW, External | Cc: |
Description (last modified by )
Hello,
I've been using Delphes as an external package for CMSSW. Basically I'm making use of the Delphes classes to access Delphes made ntuples. However, there are some pcm files which aren't being make by default and this is causing annoying error messages (see [1]) when I run CMSSW executables.
I have a suggestion on how to partially fix this problem, which I don't think actually impacts any previous functionality, so it should be a quick fix. That being said, my solution was to edit the Makefile and not the genMakefile.tcl.
My solution was to change:
@rootcint -f $@ -c -Iexternal $<
into:
@rootcint -f $@ -rmf $@.rootmap -rml $@.so -c -Iexternal $<
Does this seem like a reasonable fix? Can it be modified to be put into the genMakefile.tcl and thus get more of the Delphes classes? As I said, this is a partial fix and I wasn't able to do the same for the ExRoot classes, which still cause warnings like in [1].
Cheers,
Alexx
Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState: Missing FileEntry for ExRootAnalysis/ExRootTreeReader.h requested to autoload type ExRootTreeReader Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState: Missing FileEntry for ExRootAnalysis/ExRootTreeBranch.h requested to autoload type ExRootTreeBranch Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState: Missing FileEntry for ExRootAnalysis/ExRootTreeWriter.h requested to autoload type ExRootTreeWriter Error in cling::AutoloadingVisitor::InsertIntoAutoloadingState: Missing FileEntry for ExRootAnalysis/ExRootResult.h requested to autoload type ExRootResult
Hi Alexx,
Could you please provide a list of commands to reproduce the error messages? Do you compile or interpret your code?
I've just tried the following commands:
The .pcm files are generated:
And I can run the following commands without any error messages:
The Example*.C macros contain the following lines that load .pcm files:
Cheers,
Pavel