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

DGTAL cmake variables prefixed with DGTAL_ #1753

Open
wants to merge 12 commits into
base: main2.0
Choose a base branch
from

Conversation

dcoeurjo
Copy link
Member

PR Description

your description here

Checklist

  • Unit-test of your feature with Catch.
  • Doxygen documentation of the code completed (classes, methods, types, members...)
  • Documentation module page added or updated.
  • New entry in the ChangeLog.md added.
  • No warning raised in Debug mode.
  • All continuous integration tests pass (Github Actions)

@dcoeurjo dcoeurjo added the 2.0 label Dec 25, 2024
@dcoeurjo dcoeurjo marked this pull request as ready for review December 26, 2024 09:19
@BDoignies
Copy link
Contributor

BDoignies commented Jan 7, 2025

Shouldn't the version number also be capitalised for consistency?

DGtal/CMakeLists.txt

Lines 25 to 27 in cdccf7a

set(DGtal_VERSION_MAJOR 1)
set(DGtal_VERSION_MINOR 4)
set(DGtal_VERSION_PATCH 2)

There is also the variable 'DGtalLibDependencies' as well as functions 'DGtal_add_test' and 'DGtal_add_example' which could be capitalised. Tough, the primary intention might only be for user-exposed variables...

@dcoeurjo
Copy link
Member Author

dcoeurjo commented Jan 7, 2025

Dunno.
Actually, I don't remember if these variables are somehow required for cmake to match with the "project" name (DGtal)

@BDoignies
Copy link
Contributor

AFAIK versions for CMake are specified within the project function and can be accessed with, on most recent versions, CMAKE_PROJECT_VERSION / CMAKE_PROJECT_VERSION_{MAJOR/MINOR/PATCH/TWEAK} variables.

@dcoeurjo
Copy link
Member Author

dcoeurjo commented Jan 7, 2025

👍

@dcoeurjo
Copy link
Member Author

dcoeurjo commented Jan 7, 2025

so yes.. should be renamed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In progress
Development

Successfully merging this pull request may close these issues.

2 participants