8000 Reorganize CGNS repository structure · Issue #798 · CGNS/CGNS · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Reorganize CGNS repository structure #798

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.

Sign up for GitHub

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

Jump to bottom
Open
MicK7 opened this issue Nov 22, 2024 · 4 comments
Open

Reorganize CGNS repository structure #798

MicK7 opened this issue Nov 22, 2024 · 4 comments

Comments

@MicK7
Copy link
Contributor
MicK7 commented Nov 22, 2024

We should adopt a similar structure to hdf5 repos .
This would reorganize the repos like this:

  • src
    • adf
    • adfh
      ... *.c *.h
  • test
  • testpar
  • doxygen
  • tools
  • utils
  • config
  • UserExamples

This would mean that current tests that are under src would be moved up.
The cgnstools, utils, and tools would also move up.
@MicK7
Copy link
Contributor Author
MicK7 commented Nov 22, 2024

@brtnfld what's your opinion ?

@brtnfld
Copy link
Member
brtnfld commented Nov 22, 2024

I'm fine with the reorganization. Do you plan on moving the Autotools files to the top level, too? I always thought it strange that these files were not located there. I would call it just examples.

@MicK7
Copy link
Contributor Author
MicK7 commented Nov 23, 2024 •
edited
Loading

I'm fine with the reorganization. Do you plan on moving the Autotools files to the top level, too? I always thought it strange that these files were not located there. I would call it just examples.

Yes Autotools should be moved as well. I was thinking of waiting for the 4.5.0 release before starting any change.

@brtnfld
Copy link
Member
brtnfld commented Dec 5, 2024

We should also introduce a clang-format spec so that all the C code conforms to a specific formatting standard. It is probably easiest to do this when the number of active branches is minimal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MicK7 @brtnfld
0