-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RootReader symbols in podioDict #290
Comments
The The missing |
The behavior was introduced in #254. Specifically what seems to trigger this is defining the diff --git a/include/podio/ROOTReader.h b/include/podio/ROOTReader.h
index e91bde3..b9afe9f 100644
--- a/include/podio/ROOTReader.h
+++ b/include/podio/ROOTReader.h
@@ -35,7 +35,7 @@ class ROOTReader : public IReader {
public:
ROOTReader() = default;
- ~ROOTReader() = default;
+ ~ROOTReader();
// non-copyable
ROOTReader(const ROOTReader&) = delete;
diff --git a/src/ROOTReader.cc b/src/ROOTReader.cc
index 8c1a294..436df53 100644
--- a/src/ROOTReader.cc
+++ b/src/ROOTReader.cc
@@ -16,6 +16,9 @@
namespace podio {
+ROOTReader::~ROOTReader() {
+}
+
std::pair<TTree*, unsigned> ROOTReader::getLocalTreeAndEntry(const std::string& treename) {
auto localEntry = m_chain->LoadTree(m_eventNumber);
auto* tree = static_cast<TTree*>(m_chain->GetFile()->Get(treename.c_str())); I am not entirely sure why that makes a difference for ROOT. I will try and see if there is a way around this or if actually linking against |
make sure that there are no unknown symbols in podioDict
Created the most straightforward fix here, but I think either linking podioRootIO to the dict or adding all the root sources to it should not be a problem - ROOT is required in any case to create the dict in the first place. |
* hotfix for AIDASoft#290 make sure that there are no unknown symbols in podioDict
When using the podio master branch running anything that is linked to
podio::podioDict
prints the following warnings (errors?):Can be fixed by linking to
podio::podioRootIO
as well, but should probably not happen in the first place.Must have been introduced after v00-14-01, as that runs the above without issues.
The text was updated successfully, but these errors were encountered: