-
Notifications
You must be signed in to change notification settings - Fork 101
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
DDCore: move create_segmentation to header file so it can be used outside of DD4hep #817
Conversation
DECLARE_SEGMENTATION creates the factory entry in the library. |
Thanks for the confirmation! |
If users are calling |
Yeah, I kind of agree :) |
…remove REGISTER_SEGMENATION, re-arrange and fix segmentations
…to individual files
I re-arranged and removed some things in DDSegmentation that wasn't needed as far as I could tell. I ran into some weird namespace issue, so I added DD4hep/Factories.h to all the Segmentation and replaced the REGISTER_SEGMENTATION macro with DECLARE_SEGMENTATION. |
Moving the DECLARE_SEGMENTATION to the individual segmentations leads these calls to be part of DDCore, which means any plugin linking against DDCore has these in their components file. Will bring back the ReadoutSegmentations.cpp file in plugin and leave the DECLARE_SEGMENTATION calls commented for people creating their own segmentations, in which case they probably create their own plugin in any case and it should be OK. |
@andresailer so user code should also just replace |
@MarkusFrankATcernch as far as I can tell this is needed to be able to do
for #815
So that the segmentation_constructor is created and part of the components file?
BEGINRELEASENOTES
create_segmentation
to DDCore/include/DD4hep/detail/SegmentationsInterna.h to allow segmentation creation in other librariesENDRELEASENOTES