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

Main2.0 #467

Open
wants to merge 12 commits into
base: master
Choose a base branch
from
Open

Main2.0 #467

wants to merge 12 commits into from

Conversation

BDoignies
Copy link

Thanks a lot for contributing to DGtalTools, before submitting your PR, please fill up the description and make sure that all checkboxes are checked.

PR Description

The goal of this PR is to match changes in the branch DGTal/main2.0 (and corresponding) PRs.

Checklist

  • Doxygen documentation of the code completed (classes, methods, types, members...).
  • Main tool doxygen documentation (following existing documentation of DGtalTools documentation.
  • Check if it follows the tools structure described in CONTRIBUTING.md
  • New entry in the ChangeLog.md added.
  • Update the readme with potentially a screenshot of the tools if it applies.
  • No warning raised in Debug cmake mode (otherwise, Github Actions C.I. will fail).
  • All continuous integration tests pass (Github Actions).

@kerautret
Copy link
Member

Thanks @BDoignies, I think you miss the PR #466 but we can keep this one..

@BDoignies
Copy link
Author

Oh sorry... my bad... Haven't seen yours...

Either is fine as long as we modify accordingly the corresponding worflow file in DGtal CMake2.0 PR.

@kerautret
Copy link
Member

no problem ;) I also miss to mention you, not a big deal. There is perhaps also the contribution if you have to look (more light I think)

@BDoignies
Copy link
Author

BDoignies commented Feb 14, 2025

We should run a diff on the two PR; or directly merge them together and fix conflicts if any. After a quick look, yours look a bit more complete in the variable it modifies; but I might be missing something.

@kerautret
Copy link
Member

We should run a diff on the two PR; or directly merge them together and fix conflicts if any. After a quick look, yours look a bit more complete in the variable it modifies; but I might be missing something.

Or perhaps you can cherry-pick if you see some that you miss ;) btw the let me know if you plane to looks the related DGtalTools-contrib repository .

@BDoignies
Copy link
Author

Hey @kerautret,

I updated my PR to also modify variable WITH_VISU3D_QGLVIEWER, which was the only one missing if I am not mistaken.

I do not plan to look at DGtalTools-contrib for now. My primary focus is updating DGtal. DGtalTools was modified to make sure the GH-action run on DGtal side. There will be further updates in order to also make sure DGtalTools action also run.

Upon realease of DGtal 2.0, I will make sure, that the tools the community built are up-to-date with DGtal. If you wan't to start a PR for this, please do not forget to mention me :)

@kerautret
Copy link
Member

Perfect thanks a lot @BDoignies fine for me, I can do it no problem.
I will mention you sure ;)

At the moment, something sets the minimum standard to 14. I suspect this
is in the file included by DGtal.
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