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

Possibility to use with custom c++ version to use in intel sgx enclaves #2730

Closed
theShmoo opened this issue Apr 21, 2021 · 2 comments · Fixed by #2731
Closed

Possibility to use with custom c++ version to use in intel sgx enclaves #2730

theShmoo opened this issue Apr 21, 2021 · 2 comments · Fixed by #2731
Assignees
Labels
kind: bug release item: 🔨 further change solution: proposed fix a fix for the issue has been proposed and waits for confirmation

Comments

@theShmoo
Copy link
Contributor

theShmoo commented Apr 21, 2021

I need to use your library in an intel sgx enclave.
For that I am restricted to another standard library implementation (the one from intel)
You provide nice defines for the used c++ standard.
I use c++17 but the library of intel only has some c++11 features.
So I need to define the used standard version by my own.

I created a pull request that fixes this: #2731

theShmoo pushed a commit to theShmoo/json that referenced this issue Apr 21, 2021
if the definition of JSON_VERSION_IS_PREDEFINED is defined
the JSON_HAS_CPP_* defines are not automatically detected
@nlohmann
Copy link
Owner

Is there maybe a way to detect the used standard from that standard library?

theShmoo pushed a commit to theShmoo/json that referenced this issue Apr 21, 2021
theShmoo pushed a commit to theShmoo/json that referenced this issue Apr 21, 2021
@theShmoo
Copy link
Contributor Author

The used standard in the intel sgx c++ library is kinda c++11 so yeah it is c++11
But to be able to use language features that are later than c++11 (e.g.: keywords, ...) I build with a later standard (c++17)

@nlohmann nlohmann linked a pull request Apr 29, 2021 that will close this issue
@nlohmann nlohmann added release item: 🔨 further change solution: proposed fix a fix for the issue has been proposed and waits for confirmation labels Apr 29, 2021
@nlohmann nlohmann self-assigned this Apr 29, 2021
@nlohmann nlohmann added this to the Release 3.9.2 milestone Apr 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug release item: 🔨 further change solution: proposed fix a fix for the issue has been proposed and waits for confirmation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants