-
Notifications
You must be signed in to change notification settings - Fork 38
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
tools can only be built with appropriate nlohmann_json version #181
Comments
I'd prefer to add a cmake option and always build the nlohmann_json dependent parts except if this is explicitly turned off. |
Yeah, probably the solution that is easier to maintain. |
On that topic... EDM4hep that I build locally works well with nlohmann_json 3.11.2, but it fails when 3.10.2 was used. Are you sure that 3.10 is the minimal requirement? That's the error I get:
Moreover, I have trouble updating nlohmann_json version because it seems to be always using the version ROOT was compiled with (but maybe that compatibility is needed). |
I am not sure I have ever tried with 3.10.2, but it looks like it is not sufficient. The lowest I have tried is 3.10.5. I am not sure which version of nlohmman_json takes precedence if root was compiled with a different one (also probably depending on whether root was built with Which stack have you tried to build against? I will have another look and see whether we have to tighten that requirement. On a side note: I think the main problem this issue tried to keep track of has been solved with #185 |
I was using this docker image, it's used in the CI of the Open Data Detector. ROOT uses external installation (v 3.10.2). |
Thanks for testing. Do you need the JSON output capabilities, or would it be enough to simply make the requirements higher, so that no JSON output is built? |
I think it would make sense to have the requirement changed to 3.10.5, since it's clearly not sufficient to have 3.10. I do not need JSON output, so it was just an obstacle in the installation for me. But I just upgraded the docker image and we use now 3.10.5, so I do not have any problem anymore. |
#163 introduced a CI failure, because it tries to build a target that links to nlohmann_json, which is not explicitly discovered via
find_package
before (or at least not with an appropriate version).This should be rather easy to fix by putting the
find_package
that is currently intests
into aCMakeLists.txt
further up the directory tree and then dealing with it appropriately.The text was updated successfully, but these errors were encountered: