Skip to content

Conversation

@benegee
Copy link
Collaborator

@benegee benegee commented Dec 10, 2025

@benegee benegee changed the title Update to version 4.0.0 Update to t8code v4.0.0 Dec 10, 2025
@benegee benegee closed this Jan 7, 2026
@benegee benegee reopened this Jan 7, 2026
@benegee
Copy link
Collaborator Author

benegee commented Jan 7, 2026

Meanwhile, JuliaPackaging/Yggdrasil#12756 has been merged, i.e. we have binary packages here: https://github.com/JuliaBinaryWrappers/t8code_jll.jl

We now face the following issues:

  1. Windows cannot be run in CI anymore because we excluded Windows from the BinaryBuilder builds. ✔️
  2. MacOS was included, but fails in CI (some issue with libsc.3.0.0.dylib) https://github.com/DLR-AMR/T8code.jl/actions/runs/20780630626/job/59676973446?pr=105#step:5:146 (difficult to debug without a mac; plus mac is not officially supported by t8code, is it?)
  3. Linux on x86 fails with a t8code error:

    AssertionError: Could not read cmesh from ascii version 2, but should be able to: cmesh/testfiles/test_msh_file_vers2_ascii.msh
    (I wonder if this could actually be investigated / fixed?)

  4. Linux on x64 fails with earlier Julia versions, in particular

At least, Linux, x64, with Julia >= 1.9, runs at the moment and could be used to update downstream packages.

@spenke91 @sandro-elsweijer

@sandro-elsweijer
Copy link
Member

Nice work!
2. Officially, we only support t8code on Linux with gcc. Since we have some Windows users (I think?), this should also work, but it is not tested in our CI. Same for Mac. We do not know about any Mac users and we also do not have a CI workflow for that.
3. Yeah we had some troubles with this. It is an IO error for Gmsh msh files from version 2. It is quite old and we plan to just drop the support. I will open an issue.

I cannot say anything about point 1 and 4

@JoshuaLampert
Copy link
Collaborator

Regarding 4: I think it would be fine to bump the minimal julia version for T8code.jl to v1.10 (and run CI on it) especially because Trixi.jl already has v1.10 as minimum required and it is the current LTS.

@benegee
Copy link
Collaborator Author

benegee commented Jan 7, 2026

Thanks for your feedback!

Dropping support for all problematic platforms would be the easiest option and as a Trixi.jl person I would not be afraid to do so. I was just a little reluctant because of potential further downstream packages.

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.

3 participants