Skip to content

Add Exiv2 version to compile options display #18984

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

Merged
merged 1 commit into from
Jun 24, 2025

Conversation

victoryforce
Copy link
Collaborator

Sometimes when investigating certain bugs it can be useful to know which version of Exiv2 darktable was linked against.

@TurboGit TurboGit added this to the 5.2.1 milestone Jun 24, 2025
@TurboGit TurboGit added the scope: codebase making darktable source code easier to manage label Jun 24, 2025
@TurboGit
Copy link
Member

Ultra safe, ok for 5.2.1 on your side?

Copy link
Member

@TurboGit TurboGit left a comment

Choose a reason for hiding this comment

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

Thanks!

@victoryforce
Copy link
Collaborator Author

Ultra safe, ok for 5.2.1 on your side?

Definitely yes. Although this is not a bug fix, it can help in investigating issues that may be related to exiv2. So it would be nice to have this in 5.2.1 without delaying until winter.

@TurboGit TurboGit merged commit c7c2543 into darktable-org:master Jun 24, 2025
6 checks passed
@TurboGit
Copy link
Member

Merged in master & darktable-5.2.x branch.

@victoryforce victoryforce deleted the expose-exiv2-version branch June 24, 2025 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: codebase making darktable source code easier to manage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants