This page provides release strategoxt-0.17pre18409 of Stratego/XT Bootstrap branch. It was generated automatically on 2009-03-25 20:50:43 UTC from revision 18409 of the path /strategoxt/branches/strategoxt-fix-compilation of its Subversion repository (the XML record of the build job is available).
This source distribution requires that the following packages are also installed:
This RPM requires that the following RPM packages are also installed:
This RPM requires that the following RPM packages are also installed:
This RPM requires that the following RPM packages are also installed:
This RPM requires that the following RPM packages are also installed:
This RPM requires that the following RPM packages are also installed:
This release can be installed through Nix, a system for software deployment. It has been built for the following platforms:
You can install this package and keep it up to date by subscribing to the channel strategoxt-bootstrap-unstable by once executing
$ nix-channel --add http://releases.strategoxt.org/strategoxt-bootstrap/channels/strategoxt-bootstrap-unstable $ nix-channel --update $ nix-env -i strategoxt-0.17pre18409and then running
$ nix-channel --update $ nix-env -u strategoxt-bootstrapevery time you want to upgrade to the latest release.
Alternatively, if you have Nix 0.8 installed, and have associated the application/nix-package MIME type with the nix-install-package script in your web browser, you can install the package simply by clicking on the links below. This only works if your Nix store is in /nix/store.
The channel contains the following prebuilt packages:
Name | System |
---|---|
strategoxt-0.17pre18409 | i686-darwin |
i686-linux | |
x86_64-linux |
In case of build or usage problems with this release, please first check if there are newer releases that solve the problem. Otherwise report problems to stratego@cs.uu.nl, mentioning the full version number and a description of the platform you are building on. In case of a build problem include the part of the build log showing the error. In case of a usage problem try to narrow down the problem as much as possible and include enough information to reproduce the error.