A standalone Windows specific package (not a full multi-platform xPack),
customised for the requirements of the Eclipse Embedded CDT managed build
projects; it includes a recent version of GNU make and a recent version of
BusyBox, which provides a convenient implementation for sh/rm/echo.
In addition to the package meta data, this project also includes the build scripts.
This open source project is hosted on GitHub as
xpack-dev-tools/windows-build-tools-xpack
and provides the platform specific binaries for the
xPack Windows Build Tools.
The binaries can be installed automatically as binary xPacks or manually as portable archives.
This distribution generally follows the official make, but there is no commitment of a quick release cycle.
This section is intended as a shortcut for those who plan to use the xPack Windows Build Tools binaries. For full details please read the xPack Windows Build Tools pages.
The easiest way to install Windows Build Tools is using the binary xPack, available as
@xpack-dev-tools/windows-build-tools
from the npmjs.com registry.
The only requirement is a recent
xpm, which is a portable
Node.js command line application. To install it,
follow the instructions from the
xpm page.
With the xpm tool available, installing
the latest version of the package and adding it as
a dependency for a project is quite easy:
cd my-project
xpm init # Only at first use.
xpm install @xpack-dev-tools/windows-build-tools@latest
ls -l xpacks/.binThis command will:
- install the latest available version, into the central xPacks store, if not already there
- add symbolic links to the central store
(or
.cmdforwarders on Windows) into the localxpacks/.binfolder.
The central xPacks store is a platform dependent
folder; check the output of the xpm command for the actual
folder used on your platform).
This location is configurable via the environment variable
XPACKS_REPO_FOLDER; for more details please check the
xpm folders page.
For xPacks aware tools, like the Eclipse Embedded C/C++ plug-ins, it is also possible to install Windows Build Tools globally, in the user home folder:
xpm install --global @xpack-dev-tools/windows-build-tools@latestEclipse will automatically
identify binaries installed with
xpm and provide a convenient method to manage paths.
To remove the links from the current project:
cd my-project
xpm uninstall @xpack-dev-tools/windows-build-toolsTo completely remove the package from the global store:
xpm uninstall --global @xpack-dev-tools/windows-build-toolsFor all platforms, the xPack Windows Build Tools binaries are released as portable archives that can be installed in any location.
The archives can be downloaded from the GitHub Releases page.
For more details please read the Install page.
The version strings used by the GCC project are three number string
like 4.3.0; to this string the xPack distribution adds a four number,
but since semver allows only three numbers, all additional ones can
be added only as pre-release strings, separated by a dash,
like 4.3.0-1. When published as a npm package, the version gets
a fifth number, like 4.3.0-1.1.
Since adherance of third party packages to semver is not guaranteed,
it is recommended to use semver expressions like ^4.3.0 and ~4.3.0
with caution, and prefer exact matches, like 4.3.0-1.1.
The quick answer is to use the xPack forums; please select the correct forum.
For more details please read the Support page.
The original content is released under the MIT License, with all rights reserved to Liviu Ionescu.
The binary distributions include several open-source components; the
corresponding licenses are available in the installed
distro-info/licenses folder.
- GitHub gnu-mcu-eclipse/windows-build-tools.git
- latest release
- all releases
- latest release
- xPack @gnu-mcu-eclipse/windows-build-tools
- latest release, per month
- all releases
- latest release, per month
- individual file counters (grouped per release)
Credits to Shields IO and Somsubhra/github-release-stats.