[Feature]Outputs of abacus --version need more details #6686
Description
Background
Outputs of abacus --version only show a serial number now, which is not enough as abacus can be compiled with gcc/intel...; can run on cpu/gpu/dcu; can be grouped into different levels: https://mp.weixin.qq.com/s/bxzXcnKbqlxMHBghZXKWDw
Describe the solution you'd like
- Add more details in the outputs of
abacus --versionlike cmake options, time, third-party-library info, compilers, CFLAGS of building and so on. - Modify CMakeList.txt to build abacus executables with different names (abacus_basic/abacus_std/...) automatically regarding to the different building options.
Task list only for developers
- Notice possible changes of behavior
- Explain the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi
Notice Possible Changes of Behavior (Reminder only for developers)
No response
Notice any changes of core modules (Reminder only for developers)
No response
Notice Possible Changes of Core Modules (Reminder only for developers)
No response
Additional Context
No response
Task list for Issue attackers (only for developers)
- Review and understand the proposed feature and its importance.
- Research on the existing solutions and relevant research articles/resources.
- Discuss with the team to evaluate the feasibility of implementing the feature.
- Create a design document outlining the proposed solution and implementation details.
- Get feedback from the team on the design document.
- Develop the feature following the agreed design.
- Write unit tests and integration tests for the feature.
- Update the documentation to include the new feature.
- Perform code review and address any issues.
- Merge the feature into the main branch.
- Monitor for any issues or bugs reported by users after the feature is released.
- Address any issues or bugs reported by users and continuously improve the feature.