Skip to content
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

Exclude usage of nlohmann/json_fwd.hpp from REve [6.30] #14643

Merged
merged 3 commits into from
Feb 13, 2024

Conversation

linev
Copy link
Member

@linev linev commented Feb 9, 2024

Before llvm 13 it was not possible to parse nlohmann/json.hpp include. Therefore json_fwd.hpp was used.

But it was missing on several platforms where external nlohmann/json.hpp has to be used.

Now after llvm upgrade it is not necessary to use it.
This should simplify ROOT building and usage on platforms with installed nlohmann/json.hpp.

Also should fix #14634

It was necessary before while interpreter had problems
to correctly parse it. Starting from llvm 13 it is no longer the problem
No longer used and no longer required
@phsft-bot
Copy link
Collaborator

Starting build on ROOT-performance-centos8-multicore/soversion, ROOT-ubuntu2204/nortcxxmod, ROOT-ubuntu2004/python3, mac12arm/cxx20, windows10/default
How to customize builds

Copy link

github-actions bot commented Feb 9, 2024

Test Results

     9 files       9 suites   1d 9h 46m 31s ⏱️
 2 488 tests  2 487 ✅ 0 💤 1 ❌
21 645 runs  21 644 ✅ 0 💤 1 ❌

For more details on these failures, see this check.

Results for commit 059a4cf.

Copy link
Contributor

@osschar osschar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you Sergey!

@linev linev merged commit ae70056 into root-project:v6-30-00-patches Feb 13, 2024
11 of 15 checks passed
@linev linev deleted the json_fwd_630 branch February 13, 2024 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants