@LecrisUT Thanks for the refactoring and improvements of documents!
Just curious, how the target Spglib_symspg defined in CMakeLists.txt are resolved as Spglib::symspg as shown in example/CMakeLists.txt (not Spglib::Spglib_symspg)?
Is it a CMake functionality (if so, where is it officially documented), or resolved in spglib's side?

This I got from the discussion in Libxc. Specifically it is controlled by EXPORT_NAME here. The complete documentation of all of the cmake (target) properties is here (man cmake-properties)

Codecov Report

Base: 93.34% // Head: 93.34% // No change to project coverage 👍

Coverage data is based on head (61b4f32) compared to base (2f8b635).
Patch has no changes to coverable lines.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@           Coverage Diff            @@
##           develop     #233   +/-   ##
========================================
  Coverage    93.34%   93.34%           
========================================
  Files           15       15           
  Lines          902      902           
========================================
  Hits           842      842           
  Misses          60       60           

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Rebased it onto develop and cleaned up the documentation, let me know if you find it cleaner now.

A few things though:

• @atztogo Can you make the example_c and/or example_f08 more minimal so that it has more realistic example? Also have a very simple example in the main README of what spglib can do.
• @atztogo I have removed your tetrahedron.c example because it couldn't be compiled without tetrahedron.h, is it ok, or can you otherwise add all the necessary files here?
• Is the mailing list in sourceforge (https://sourceforge.net/p/spglib/mailman/) still active? Should we get rid of it and use Github and maybe gitter/matrix/irc for more live channels?

@LecrisUT, @lan496, I have a minor question. I just recently know cmake option of -B. Currently the spglib documentation it is written like below.

$ mkdir build
$ cd build
$ cmake .. ${CMAKE_OPTIONS}
$ cmake --build .
$ cmake --install .

But it can be also

$ cmake -B build ${CMAKE_OPTIONS} .
$ cmake --build build
$ cmake --install build

Which do you prefer?

• @atztogo Can you make the example_c and/or example_f08 more minimal so that it has more realistic example? Also have a very simple example in the main README of what spglib can do.

I agree. It was also used as tests. We have (C) and are preparing (Fortran) tests, so I agree. Can it be written in an issue?

• @atztogo I have removed your tetrahedron.c example because it couldn't be compiled without tetrahedron.h, is it ok, or can you otherwise add all the necessary files here?

OK! Thanks.

• Is the mailing list in sourceforge (https://sourceforge.net/p/spglib/mailman/) still active? Should we get rid of it and use Github and maybe gitter/matrix/irc for more live channels?

Sourceforge mailing list is not at all very active. We can use github instead. I have no idea about gitter/matrix/irc. Only github is not enough?

Which do you prefer?

@atztogo I like the latter because it needs fewer commands, although a bit newer CMake >= 3.13 is required.

@LecrisUT, @lan496, I have a minor question. I just recently know cmake option of -B. Currently the spglib documentation it is written like below.

Which do you prefer?

Oh yeah, I completely forget about -B. I'm also ok with rewriting it to that.

I have no idea about gitter/matrix/irc. Only github is not enough?

Sure, only github is fine. The others are like slack, but open sourced. All those 3 are interoperable. I'm always reachable on matrix if someone wants to discuss something there.