slim is currently using Autotools as the build tool, but it's difficult to maintain the existing m4 scripts
and configure.ac file. Therefore, switching to a different build tool becomes considerable, and one possible option is CMake. Here is some advantages comparing CMake and Autotools:
Cross-platform support: While Autotools has good support for Unix-based systems, it can be more challenging to use on other platforms such as Windows. CMake, on the other hand, has better cross-platform support and can generate build files for a variety of operating systems.
Integration with modern build systems: Many modern build systems, such as Visual Studio, Xcode, and Ninja, have built-in support for CMake. By using CMake, it becomes easier to integrate with these systems and take advantage of their features.
Easier to use: CMake uses a simpler syntax compared to Autotools, which can make it easier for developers to understand and modify the build process.
Current Progress
[x] Basic Compilation
[ ] Installation
[ ] Doxygen
[ ] Library Checks
[ ] LibRT (defaults to true now)
[x] Others (Keep true or not to check for unused definitions)
[ ] Keyword Checks
[ ] __thread (Consider use thread_local instead in future refactoring)
[x] Others (Keep true or not to check for unused definitions)
Motivation
slim is currently using Autotools as the build tool, but it's difficult to maintain the existing m4 scripts and configure.ac file. Therefore, switching to a different build tool becomes considerable, and one possible option is CMake. Here is some advantages comparing CMake and Autotools:
Current Progress
thread_localinstead in future refactoring)