This binary xPack installs the platform specific binaries for GNU MCU Eclipse Windows Build Tools.
The source files of the xPack project are publicly available from GitHub.
This section is intended for developers who plan to use the Windows Build Tools.
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.
The xPack is available as
@gnu-mcu-eclipse/windows-build-tools
from the public npmjs.com
repository; with xpm
available, installing
the latest version of the package is quite easy:
$ npm update --global xpm
$ xpm install @gnu-mcu-eclipse/windows-build-tools --global
Global xPacks are always installed in the user home folder, even on GNU/Linux
or macOS, and do not require sudo
.
The GNU MCU Eclipse plug-ins automatically identify binaries installed with
xpm
and provide a convenient method to manage paths.
To remove the installed xPack, the command is similar:
$ xpm uninstall @gnu-mcu-eclipse/windows-build-tools --global
(Note: not yet implemented. As a temporary workaround, simply remove the
xPacks/@gnu-mcu-eclipse/windows-build-tools
folder, or the versions subfolders.)
The few xPack source files are available from GitHub:
$ git clone https://github.com/gnu-mcu-eclipse/windows-build-tools-xpack.git windows-build-tools-xpack.git
The binaries are not stored on the npmjs.com
server, but are downloaded from
the releases
section of the gnu-mcu-eclipse/windows-build-tools
GitHub project.
- open releases and select the latest release
- update the
baseUrl:
with the file URLs (including the tag/version) - from the blog post, copy the SHA & file names
- commit all changes, use a message like
package.json: update urls for 8.2.0-2.2 release
(withoutv
) - update
CHANGELOG.md
; commit with a message like CHANGELOG: prepare v8.2.0-2.2.1 npm version 8.2.0-2.2.1
- push all changes to GitHub
npm publish
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 licenses
folder.