-
Notifications
You must be signed in to change notification settings - Fork 14
COMP: Use modern macro for name of class #126
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
Conversation
|
@dzenanz This is part of an effort to create a v5.4.2.1 release that allows Slicer to build with ITK_LEGACY_REMOVE and ITK_FUTURE_LEGACY_REMOVE turned on. It is an intermediate refactoring that is upstream compatible but allows Slicer to catch up more slowly. |
|
@dzenanz Part of the future updates needed to build Slicer with future code recommendationsl |
53b8a4f to
9fdec0a
Compare
|
This sounds like WASM part needs to be updated to use a newer base image: |
|
Is |
|
Yes, it was added in Dec 2023. |
|
It is there already in v5.4.0: |
|
I will rebase, follow-up. |
|
Can you rebase this Hans? |
2450049 to
8ca113c
Compare
When preparing for the future with ITK by setting ITK_FUTURE_LEGACY_REMOVE:BOOL=ON ITK_LEGACY_REMOVEBOOL=ON The future preferred macro should be used │ - itkTypeMacro │ + itkOverrideGetNameOfClassMacro
Update source to match newer ITK style guidelines.
6d8a46d to
4a552c6
Compare
|
@dzenanz Rebased. |
|
Matt, would changes from InsightSoftwareConsortium/ITKMeshToPolyData#77 work here? |
|
Wasm updates for ITK 5.4.2 are here: #130 |
When preparing for the future with ITK by setting
ITK_FUTURE_LEGACY_REMOVE:BOOL=ON
ITK_LEGACY_REMOVEBOOL=ON
The future preferred macro should be used
│ - itkTypeMacro
│ + itkOverrideGetNameOfClassMacro