# build tools Build tools consist of CLIs, SDKs, binaries, plugins, or extensions that enable CI/CD pipelines to build software from code. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## HTML Minifier: A 12-Year Journey Building and Maintaining an Open Source Tool DevFeed: [HTML Minifier: A 12-Year Journey Building and Maintaining an Open Source Tool]() Original publisher: [Read original article]() Author: Dean Hume Published: 2025-10-30T14:49:50Z Content type: opinion Language: en Sources: [Dean Hume]() Topics: [HTML](), [Web](), [Open Source](), [ASP.NET](), [Angular](), [build tools]() Tags: [angular](), [asp-net](), [build-tools](), [html](), [journey](), [open-source](), [performance](), [web-performance]() ### AI overview The author reflects on developing and maintaining an open-source HTML Minifier over 12 years. The tool reduces HTML size by removing unnecessary whitespace, line breaks, and comments, and evolved with framework compatibility, recursive scanning, multi-file support, line-length controls, and performance metrics. ### Source excerpt Discover the 12-year journey behind HTML Minifier an open source tool that helped developers optimize web performance and reduce page load times. ## ReactOS in 2020 DevFeed: [ReactOS in 2020]() Original publisher: [Read original article]() Published: 2021-01-02T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [build tools](), [CMake](), [Filesystems](), [gcc](), [Shell](), [clang](), [Command-line interface](), [MSVC](), [GitHub]() Tags: [c-plus-plus](), [ci](), [clang](), [cmake](), [command-line](), [filesystem](), [free](), [gcc](), [github](), [kernel](), [msvc](), [open-source](), [os](), [react](), [reactos](), [shell](), [tooling](), [upgrade](), [win32](), [winapi]() ### AI overview A 2020 retrospective on ReactOS reports bug fixes, new instabilities, full-time kernel hires, shell improvements, RAPPS application-manager enhancements, and upgrades to its compiler and build tooling. It covers GCC 8.4, CMake 3.17, restored Clang CI builds, reduced older MSVC support, and a move to the C99 standard. ### Source excerpt Despite all the turbulence, it has been quite a productive year for ReactOS. Many bugs and instabilities were resolved, many more have been introduced. This year we hired two kernel developers full-time, this happened for the first time in the project's history. The post highlights some of the changes which may be interesting to the community. Shell changes Shell hasn't seen much attention recently, due to most of the work being concentrated in the kernel, but there are still some useful fixes and feature implementations: ## ReactOS Build Environment 2.2 released DevFeed: [ReactOS Build Environment 2.2 released]() Original publisher: [Read original article]() Published: 2020-05-01T00:00:00Z Content type: release Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [build tools](), [gcc](), [toolchain](), [Parser](), [C](), [C++](), [CMake](), [Visual Studio](), [Linux](), [macOS](), [Windows]() Tags: [binutils](), [build](), [c](), [c-plus-plus](), [cmake](), [compiler](), [free](), [gcc](), [linux](), [macos](), [open-source](), [os](), [react](), [reactos](), [toolchain](), [visual-studio](), [win32](), [winapi]() ### AI overview ReactOS Build Environment 2.2 upgrades the project's compiler and build tools, replacing GCC 4.7.2 with GCC 8.4.0. The release improves diagnostics, adds support for newer C and C++ standards, includes Bison and Flex, and updates the remaining toolchain. ### Source excerpt The ReactOS Build Environment (RosBE), our curated set of compilers and build tools, has just received a major upgrade. After more than 7 years of using the same and now ancient GCC 4.7.2, ReactOS is finally going to be built with the help of a modern compiler (GCC 8.4.0). Among other things, the new version better detects programming mistakes like improperly sized buffers, and comes with improved error messages to pinpoint such mistakes to the corresponding position in code. ## Android version codes in Gradle build variants and generated configuration DevFeed: [Android version codes in Gradle build variants and generated configuration]() Original publisher: [Read original article]() Published: 2019-07-04T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Android](), [version](), [Gradle](), [build tools](), [Code]() Tags: [android](), [build](), [build-tools](), [gradle](), [version]() ### AI overview This article explains how Android version codes are configured in build.gradle, accessed through BuildConfig and PackageManager, and overridden for specific build variants. It describes a discrepancy in which BuildConfig.VERSION_CODE and the processed AndroidManifest can receive different values because separate build-tool tasks use different sources. ### Source excerpt Introduction Version code is a special integer value which works as an internal version number. It is not visible to end users. Android system uses this number to protect against application downgrades -- it is not possible to install new application with version code lower than in currently installed application. Developers can use version code for example for doing specific tasks on updating to specific version. Version code is placed inside AndroidManifest, but usually it is inside *defaultConfig *in build.gradle (from where it is populated to *AndroidManifest *during assemble). Also it is possible to access version code from generated BuildConfig.VERSION_CODE.