In C++ modules globally unique module names seem to be unavoidable
3 days ago
- #Build Systems
- #Modules
- #C++
- C++ module files and importing them are complicated due to lack of strict requirements in the C++ standard.
- Different approaches for module integration exist, including custom JSON files and socket server daemons.
- A common project setup involves a single executable and multiple static libraries, some internal and some external.
- Converting libraries to modules requires unique module names to avoid conflicts, especially with external dependencies.
- Having multiple modules with the same name in an executable leads to broken code (IFNDR).
- Module names must be globally unique to ensure compatibility and avoid technical issues.
- A simplified build setup involves a single directory for modules with unique names, eliminating the need for complex module mappers.
- Module files are not stable and are not meant to replace headers for prebuilt libraries in the near future.