-
Notifications
You must be signed in to change notification settings - Fork 36
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
Allow forcing of bundled rapidjson #125
Comments
Hello Andre, I think you are aware already by now, but I'll post here again the summary. With the discussion that started in the ROOT project (root-project/root#17190) and crossed-over to Davix (#130), I went ahead and patched the Davix-bundled RapidJson library (thanks to #129). Since the latest officially released This is documented and tracked further here: DMC-1426 / DMC-1427 Over the long-term, the plan is to stop using RapidJson altogether, in favor of a more widely-supported library, such as Cheers, |
Ok, no problem if you always use the bundled rapidjson. |
Still good for us 👍 :) |
Yes, you could use the default, bundled RapidJSON library in ROOT and be away from all this headache. Over the (not-so)long-term, I plan to drop RapidJSON completely from Davix and switch to another JSON library, such as |
Do you mean the bundled Davix in ROOT? |
Yes, I mean when compiling ROOT, you can use the Davix-bundled RapidJSON to compile the ROOT-bundled Davix 🙂 But my second question was general: which JSON library does ROOT use? Cheers, |
No, no, no I don't want to use rapidjson from ROOT to build Davix, and then use Davix inside ROOT. We want to have Davix stand alone for some reason. We also might want to not use the Davix version that comes along with Root. Yes, ROOT does use nlohman json, I don't know if they use another one as well. |
If you would like to use a library that is always external, while allowing ROOT to build Davix as builtin, you can try nlohmann_json. See here the software that ROOT has bundled to avoid taking from the system when necessary. Cheers, |
Hello, @amadio I see that nlohmann-json is up-to-date in EPEL. I plan to switch Davix to this package (if it's easy to use). My goal is to remove the bundled dependencies and use only system ones |
Dear Developers,
Would it be possible to add a cmake option to let us force the use of the bundled or external rapid json?
davix/CMakeLists.txt
Line 100 in f41e619
It would be unfortunate if we accidentally pick up one or the other depending on the build order of our software stacks (In my case building LCG software stacks).
Thanks!
The text was updated successfully, but these errors were encountered: