This is the initial 2.0 release of the Singularity Research Development Kit (RDK), including many major updates to the platform since its initial release in March, based on Change Set 17067. The 2.0 release of the Singularity RDK is based on the original release and features an extensive list of bug fixes and new features. Some of most notable are:
- Support for AMD64 64-bit platforms
- Updates to the Bartok MSIL-to-native compiler and the Sing# compiler
- A new, more modern and extensible bootloader
- Several new applications and application documentation
- Eventing support
- More extensive ACPI support
- A unit testing library
- A ramdisk device
- An SMB client service
- Can now check out the most recent version of the Singularity RDK directly from CodePlex source control
There are two downloads:
- Singularity RDK 2.0 CD image.World.zip: A ZIP archive containing a bootable ISO for a complete compiled build of Singularity for the 32-bit x86 platform. This can be mounted in Virtual PC (a .vmc file is included) or burned to a disc and used to boot a real PC.
- Singularity RDK 2.0 Source.zip: A ZIP archive containing the complete source tree for Singularity, allowing you to build your own binaries, create your own applications and drivers, and make your own custom kernel modifications. To minimize download time, this archive does not include debug symbols for build tools; if you want these, you can use the Download link for Change Set 17067 on the Source Code tab.
Future development plans
Beginning with RDK 2.0, we're moving to a model of incremental releases where the codebase will grow and improve more gradually over time.
We're also looking to increase community participation in the RDK 2 - so if you're using the RDK for something cool, let us know on the Discussions tab, and submit Patches on the Source Code tab. Patches will be integrated into the codebase, so that other RDK users can take advantage of your work. We will grant Developer permissions
to frequent contributors to help streamline their contributions and let the users drive the future of the RDK.