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

Cmake version depends on version 3.8 due to nlohmann/json #194

Closed
phunkyfish opened this issue Mar 6, 2019 · 7 comments
Closed

Cmake version depends on version 3.8 due to nlohmann/json #194

phunkyfish opened this issue Mar 6, 2019 · 7 comments

Comments

@phunkyfish
Copy link
Member

Causes issues when building OSMC and for users on Ubuntu as build platform. Creating issue instead of proposed PR: #190

Upstream issue here: nlohmann/json#1498
Upstream PR which relaxes the dependency: nlohmann/json#1441

@phunkyfish
Copy link
Member Author

@StormTrooper @samnazarko will track from here instead of proposed PR.

The upstream PR which relaxed the dependency was incorrect, there is a new one proposed.

@samnazarko
Copy link

samnazarko commented Mar 17, 2019

Do we have some progress on this? Anything we can do to help on our side?

Edit: this is now fixed

S

@phunkyfish
Copy link
Member Author

phunkyfish commented Mar 17, 2019

So now we just need a release of nlohmann/json.

I would advise creating an upstream issue stating what you need and why it’s important. If it’s not ready for the next major release they might do a minor release just including the fix you need.

No harm in asking.

@StormTrooper
Copy link

StormTrooper commented Mar 21, 2019

3.6.1 has been pushed out (CMake Issue actually fixed in 3.6.0)

@phunkyfish
Copy link
Member Author

phunkyfish commented Mar 21, 2019

Can you try updating the zip version and SHA hash here:

nlohmann-json https://github.com/nlohmann/json/archive/v3.5.0.tar.gz

And here:

e0b1fc6cc6ca05706cce99118a87aca5248bd9db3113e703023d23f044995c1d

to see if it solves your issues?

The checksum for 3.6.1 will be: 80c45b090e40bf3d7a7f2a6e9f36206d3ff710acfa8d8cc1f8c763bb3075e22e

In the meantime I will test using 3.6.1.

@StormTrooper
Copy link

Updating to 3.6.1 fixes the issue. Build completes successfully.

@phunkyfish
Copy link
Member Author

Great, will include the update in the next PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants