XTChain seems to contain unnecessary tools, like MinGW integration. We do not use it to build Win32 applications, and ExectOS should have its own runtime library. Therefore, MinGW should not be needed. There may be more such unnecessary tools. The goal of the task is to slim down the toolchain by identifying all the really needed tools and removing those that are not used.
XTChain seems to contain unnecessary tools, like MinGW integration. We do not use it to build Win32 applications, and ExectOS should have its own runtime library. Therefore, MinGW should not be needed. There may be more such unnecessary tools. The goal of the task is to slim down the toolchain by identifying all the really needed tools and removing those that are not used.
harraiken
added this to the XT Toolchain Development Board project 2025-03-19 15:01:37 +01:00
harraiken
added the IDEA label 2025-03-19 15:02:16 +01:00
The XTChain-built version of CMake introduces a custom watermark by modifying the CMake_VERSION variable. This change is introduced in the patches\cmake\v3.29.3\001-add-xtc-version-suffix.patch patch.
The only functional difference in XTChain’s CMake build is the version suffix, which is not a valid reason to maintain a custom-built version.
Recommended Steps
Deprecate XTChain-built CMake in favor of system-installed CMake.
Remove watermark patches and update build instructions to reflect the new dependency installation strategy.
Ensure CI/CD compatibility by validating that system package managers can reliably provide CMake for all supported platforms.
# XTChain's CMake
The XTChain-built version of CMake introduces a custom watermark by modifying the `CMake_VERSION` variable. This change is introduced in the `patches\cmake\v3.29.3\001-add-xtc-version-suffix.patch` patch.
The only functional difference in XTChain’s CMake build is the version suffix, which is not a valid reason to maintain a custom-built version.
### **Recommended Steps**
1. **Deprecate XTChain-built CMake** in favor of system-installed CMake.
2. **Remove watermark patches** and update build instructions to reflect the new dependency installation strategy.
3. **Ensure CI/CD compatibility** by validating that system package managers can reliably provide CMake for all supported platforms.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
XTChain seems to contain unnecessary tools, like MinGW integration. We do not use it to build Win32 applications, and ExectOS should have its own runtime library. Therefore, MinGW should not be needed. There may be more such unnecessary tools. The goal of the task is to slim down the toolchain by identifying all the really needed tools and removing those that are not used.
XTChain's CMake
The XTChain-built version of CMake introduces a custom watermark by modifying the
CMake_VERSIONvariable. This change is introduced in thepatches\cmake\v3.29.3\001-add-xtc-version-suffix.patchpatch.The only functional difference in XTChain’s CMake build is the version suffix, which is not a valid reason to maintain a custom-built version.
Recommended Steps
#10