Skip to content

Update SimpleITK release - #118

Closed
zivy wants to merge 2 commits into
SimpleITK:mainfrom
zivy:updateRelease
Closed

Update SimpleITK release#118
zivy wants to merge 2 commits into
SimpleITK:mainfrom
zivy:updateRelease

Conversation

@zivy

@zivy zivy commented Aug 7, 2026

Copy link
Copy Markdown
Member

No description provided.

@zivy
zivy force-pushed the updateRelease branch 3 times, most recently from 6976ddb to 3ed1223 Compare August 9, 2026 23:06
@blowekamp

Copy link
Copy Markdown
Member

It looks like the error message in SimpleITK for the -std flag should be updated.

You no not need to explicitly enable C++17 for SimpleITK. This change is heading down the wrong path the address the error.

@zivy
zivy force-pushed the updateRelease branch 4 times, most recently from a5eeec2 to f7b824b Compare August 10, 2026 23:30
@zivy
zivy requested a review from blowekamp August 11, 2026 12:54
@zivy

zivy commented Aug 11, 2026

Copy link
Copy Markdown
Member Author

HI @blowekamp, your observation was correct. The actual issue was with the AlmaLinux8 gcc version which was too old (version 8). It did have support for C++17, but that wasn't complete. Upgrading to gcc 13 resolved the issue.

Comment thread .github/workflows/main.yml Outdated
harfbuzz-devel fribidi-devel libssh2-devel \
curl tar
# Prepend GCC 13 to PATH so all subsequent steps (including R) use it
echo "/opt/rh/gcc-toolset-13/root/usr/bin" >> $GITHUB_PATH

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

There may be other env variable that should be set. The best practice is to run source scl_source enable gcc-toolset-13. That could be done right before the build to enable this tool change, it think.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

done and force pushed

Install GCC 13 for full C++17 compatibility on
AlmaLinux 8. Replaces the default GCC 8 which
has partial C++17 support which isn't sufficient
for modern ITK.
@blowekamp

Copy link
Copy Markdown
Member

What is the plan and strategy to manage 2.5 patch release along with 3.0 pre-releases? Separate branches? Some type of configuration?

@zivy

zivy commented Aug 11, 2026

Copy link
Copy Markdown
Member Author

Closing this PR in favor of #119.
3.0 pre-releases will go on their own branch and not on main.

@zivy zivy closed this Aug 11, 2026
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