Skip to content

Use new gitlab remote to clone Eigen.#1631

Merged
jdumas merged 1 commit intolibigl:masterfrom
BruegelN:update_Eigen-remoteURL
Oct 18, 2020
Merged

Use new gitlab remote to clone Eigen.#1631
jdumas merged 1 commit intolibigl:masterfrom
BruegelN:update_Eigen-remoteURL

Conversation

@BruegelN
Copy link
Copy Markdown
Contributor

As Eigen is now on GitLab.com change path to Eigen's git repository in cmake.
The old github repo is only kept for convenience but does not receive further updates.
Using the repo on gitlab.com it's possible to change to the latest Eigen version 3.3.8 (ChangeLog )
Whether updating to Eigen 3.3.8 is a good idea/worth it or not is another story.

Check all that apply (change to [x])

  • All changes meet libigl style-guidelines.
  • Adds new .cpp file.
  • Adds corresponding unit test.
  • This is a minor change.

Copy link
Copy Markdown
Collaborator

@jdumas jdumas left a comment

Choose a reason for hiding this comment

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

Thanks! I think we should stay compatible with Eigen 3.3.7 for a while longer, but at least it should be easy for the user to use a newer version if they want.

@jdumas jdumas merged commit a2a1479 into libigl:master Oct 18, 2020
@BruegelN
Copy link
Copy Markdown
Contributor Author

Agree, @jdumas!
The ChangeLog for Eigen 3.3.8 mentions quite a lot bugfixes but I fully understand the risks of upgrading such an essential component!

BTW: fixes #1437

@jdumas
Copy link
Copy Markdown
Collaborator

jdumas commented Oct 19, 2020

Yeah it's more a question that we should not use newer Eigen features right of the bat, as it might be problematic to integrate into codebases that haven't updated their Eigen version yet. Of course if you're a product using libigl/Eigen you should update if possible, but that part is not up to us.

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

Successfully merging this pull request may close these issues.

2 participants