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

Fix vtk compiler errors #567

Merged
merged 3 commits into from
May 31, 2023
Merged

Fix vtk compiler errors #567

merged 3 commits into from
May 31, 2023

Conversation

sandro-elsweijer
Copy link
Collaborator

Describe your changes here:
The main branch is not compilable with vtk

All these boxes must be checked by the reviewers before merging the pull request:

As a reviewer please read through all the code lines and make sure that the code is fully understood, bug free, well-documented and well-structured.

General

  • The reviewer executed the new code features at least once and checked the results manually

  • The code follows the t8code coding guidelines

  • New source/header files are properly added to the Makefiles

  • The code is well documented

  • All function declarations, structs/classes and their members have a proper doxygen documentation

  • All new algorithms and data structures are sufficiently optimal in terms of memory and runtime (If this should be merged, but there is still potential for optimization, create a new issue)

Tests

  • The code is covered in an existing or new test case using Google Test

Github action

  • The code compiles without warning in debugging and release mode, with and without MPI (this should be executed automatically in a github action)

  • All tests pass (in various configurations, this should be executed automatically in a github action)

    If the Pull request introduces code that is not covered by the github action (for example coupling with a new library):

    • Should this use case be added to the github action?
    • If not, does the specific use case compile and all tests pass (check manually)

Scripts and Wiki

  • If a new directory with source-files is added, it must be covered by the script/find_all_source_files.scp to check the indentation of these files.
  • New Datatypes are added to t8indent_custom_datatypes.txt
  • If this PR introduces a new feature, it must be covered in an example/tutorial and a Wiki article.

Licence

  • The author added a BSD statement to doc/ (or already has one)

@sandro-elsweijer sandro-elsweijer added shouldn't take long Can be resolved in under 30 mins critical Should be handled ASAP labels May 24, 2023
@jmark
Copy link
Collaborator

jmark commented May 24, 2023

I can compile the main branch with enabled vtk without any issues. I followed the instructions in the wiki: https://github.com/DLR-AMR/t8code/wiki/Installation-of-VTK.

Or are you compiling with pedantic and similar?

@sandro-elsweijer
Copy link
Collaborator Author

sandro-elsweijer commented May 24, 2023

I can compile the main branch with enabled vtk without any issues. I followed the instructions in the wiki: https://github.com/DLR-AMR/t8code/wiki/Installation-of-VTK.

Or are you compiling with pedantic and similar?

This is only an Issue with VTK < 9.2. This can be observed here: https://github.com/DLR-AMR/t8code/actions/runs/4973174875/jobs/8898841856
This also fixes the compiler warnings caused by uninitialized variables

@Davknapp Davknapp merged commit 480af7c into main May 31, 2023
3 checks passed
@Davknapp Davknapp deleted the fix-vtk_compiler_errors branch May 31, 2023 12:56
jfussbro pushed a commit to jfussbro/t8code that referenced this pull request Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical Should be handled ASAP shouldn't take long Can be resolved in under 30 mins
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants