Blog
See important news from the RuyiSDK team at any time
RuyiSDK 0.15 is now released. The corresponding package manager version is also 0.15.
You can download the RuyiSDK package manager from one of the following locations:
This update mainly consists of the following changes. Happy hacking!
-
Getting prepared for multi-language support: in cases localized content
is requested, such as manual download instructions for software packages,
ruyi will now try to choose an appropriate locale if your system locale
does not exactly match one of the available locales for the given content.
For example: if you configure your system locale as Singaporean English
(en_SG), but one piece of content is only available in U.S. English
(en_US) and China Mainland Chinese (zh_CN), then in this case ruyi
0.15.0 will show you the en_US version instead of crash.
-
ruyi can now be built without a Docker dependency, for distribution
packagers' convenience, and for those users wanting to try out ruyi but
are not running officially supported architecture and/or OS.
Please note that as the majority of official RuyiSDK Software Repository
packages are distributed in binary form, users who want to run ruyi
on non-officially-supported systems have to get organized, and maintain
their own software repository. The RuyiSDK team cannot guarantee user
experience under such circumstance.
- The repository layout is no longer compatible with
ruyi 0.7.0 or lower;
such users should upgrade right now.
- Version 0.3.0 of
emulator/box64-upstream is now packaged.
- The guide for running WPS Office with Box64 has been revised.
- The Ruyi Device Provisioner (
ruyi device provision) now supports the following device model and system:
- Canaan Kendryte K230D: CanMV Linux SDK image packaged by RuyiSDK with permission, with demo programs, available in two ABIs -- LP64 and RV64ILP32.
RuyiSDK 0.14 is now released. The corresponding package manager version is also 0.14.
You can download the RuyiSDK package manager from one of the following locations:
This update mainly consists of the following changes. Happy hacking!
- An plugin architecture is officially introduced into
ruyi: profile-related
handling for ruyi virtual environments are now entirely taken care of by
plugins.
- Unpacking of Debian package archives --
*.deb files is now supported.
- Improved handling of "pre-release versions" again: previously
ruyi will
mistreat versions that contain non-digit character(s) in their suffixes.
The bug has not had a chance to trigger with the current content of RuyiSDK
repository though.
- Fixed
pygit2 build failure on riscv64 Python 3.12: previously one would
have to manually intervene after pygit2 started to build, but before it
tried to invoke setup.py inside its virtual environment, by installing
setuptools inside the venv -- the package is no longer automatically
installed in venvs from Python 3.12 on.
- The architecture simulator Box64 built from upstream sources is added:
emulator/box64-upstream.
- The office suite
extra/wps-office is added.
Attention: due to its commercial nature, you will have to accept an EULA
on the first use of the software.
- You can now run WPS Office on your RISC-V desktop with the help of Box64.
Please follow the guide available via
ruyi news for trying out.
Please run ruyi update to pull in the update after upgrading the RuyiSDK
package manager.
To support devices that require manual intervention during provisioning, and
whose images have to be downloaded manually, the RuyiSDK Device Provisioner is
now being refactored into a plugin-based architecture. However in this
development cycle we had to prioritize the Box64 & WPS Office PoC work;
we still expect to finish the device provisioner refactoring in a future
release. Older versions of the device provisioner will
stop working at that time; please upgrade before you test.
得益于 Box64 RISC-V 移植工作的进展，在 RISC-V Linux 桌面发行版上运行 WPS
Office 等常见 x86 二进制软件已成为可能。RuyiSDK 正在开展此方面的集成工作；
按以下的步骤操作，您将能先行一步感受 RISC-V 办公体验。
我们假定您在进行以下操作之前，已经升级到了 ruyi 0.14.0 或更高的版本，
并执行了 ruyi update 以将软件源信息同步到最新。
为叙述方便，设您的 $HOME 为 /home/foo，架构（uname -m 输出）为
riscv64，使用 sudo 提权。
由于 Box64 RISC-V 支持进展迅速，目前（2024 年 7 月初）很多功能改进没有在
其最新稳定版本得到体现。我们打包了 Box64 的开发快照版本；为了能够安装此版本，
您需要配置 ruyi 以使其在安装软件包时考虑预发布版本。
- 如果
~/.config/ruyi 目录不存在，则创建之。
- 编辑
~/.config/ruyi/config.toml。
[packages]
prereleases = true
按照 RuyiSDK 软件包的命名习惯，从 Box64 的上游（而非 PLCT 或某些厂商的 fork）
构建的 Box64 二进制包，名字叫 box64-upstream。
ruyi install box64-upstream
记下安装路径。
由于 WPS Office 的打包方式特殊，它只能从开发商提供的启动器脚本被间接拉起，
而不能直接交由 Box64 启动。因此您需要确保您的系统支持 binfmt_misc：
如果不支持，接下来的操作会失败。
不同 Linux 发行版的 binfmt_misc 配置方式不尽相同，以下针对采用 systemd
的系统叙述。您可以根据自身情况自行调整。
ls /home/foo/.local/share/ruyi/binaries/riscv64/box64-upstream-0.2.8-ruyi.20240702/bin/box64
nano /home/foo/.local/share/ruyi/binaries/riscv64/box64-upstream-0.2.8-ruyi.20240702/etc/binfmt.d/box64.conf
sudo cp /home/foo/.local/share/ruyi/binaries/riscv64/box64-upstream-0.2.8-ruyi.20240702/etc/binfmt.d/box64.conf /etc/binfmt.d/box64.conf
sudo systemctl restart systemd-binfmt
cat /proc/sys/fs/binfmt_misc/box64
由于 Box64 主要面向游戏等软件的模拟，而这些软件基本都自带所有依赖，所以 Box64
本身基本没有自带什么 x86 运行时库。WPS Office 作为一个预期被系统包管理器管理的
桌面应用，Box64 自带的少量 x86 运行时库无法满足它的需求，因此我们需要自行准备
x86 环境。
wget https://mirror.iscas.ac.cn/ruyisdk/dist/temp/debian-bookworm.gui.20240705.amd64.tar.zst
sudo mkdir /opt/debian-bookworm.amd64
pushd /opt/debian-bookworm.amd64
tar -xf ~/Downloads/debian-bookworm.gui.20240705.amd64.tar.zst
popd
强制安装 x86_64 架构的 WPS Office 软件包：
ruyi install --host x86_64 wps-office
由于 WPS Office 官方下载页面的限制，ruyi 无法自动下载安装包。
请按照提示信息操作，之后重新执行该命令以安装。
由于 WPS Office 预期自身被系统包管理器管理，它的启动器脚本假定了自身的安装路径
为 /opt/kingsoft/wps-office，需要为它们打补丁。
pushd /home/foo/.local/share/ruyi/binaries/x86_64/wps-office-11.1.0-r.11719
sed -i "s@gInstallPath=/@gInstallPath=$(pwd)/@" ./usr/bin/*
popd
准备工作终于完成，现在将所有部分串起来：
export BOX64_EMULATED_LIBS=libsqlite3.so.0
export BOX64_LD_LIBRARY_PATH=/opt/debian-bookworm.amd64/usr/lib/x86_64-linux-gnu
/home/foo/.local/share/ruyi/binaries/x86_64/wps-office-11.1.0-r.11719/usr/bin/wps
以上是 RuyiSDK 对 RISC-V 二进制翻译 x86 软件的初步集成成果。
今后我们仍将迭代这一过程的用户体验，以期用户在 RISC-V 系统上运行需要的应用
更加方便。
RuyiSDK 0.13 is now released. The corresponding package manager version is also 0.13.
You can download the RuyiSDK package manager from one of the following locations:
This update mainly consists of the following changes. Happy hacking!
- Fixed issue #158: The two
versions of the
coremark package formerly had different directory layout
after extraction. Now both are "flattened" into the current directory.
- Fixed issue #159:
inconsistency in handling of "pre-release" versions.
- Following the official release of Python 3.12, the official
ruyi binaries
are now built in a Python 3.12 environment.
- Preparatory work towards introduction of plugin architecture: support for
the Starlark language has been introduced, with CI builds also supported.
Starlark is a minimal dialect of Python that is widely adopted by build
systems such as Bazel and BUCK. The choice of Starlark as the RuyiSDK
Package Manager plugin language is meant to enable all developers familiar
with the Python language to develop RuyiSDK Package Manager plugins with a
familiar syntax.
To support devices that require manual intervention during provisioning, and
whose images have to be downloaded manually, the RuyiSDK Device Provisioner is
now being refactored into a plugin-based architecture, with the next version
expected to be fit for testing. Older versions of the device provisioner will
stop working at that time; please upgrade before you test.
RuyiSDK 0.12 is now released. The corresponding package manager version is also 0.12.
You can download the RuyiSDK package manager from one of the following locations:
This update mainly consists of the following changes. Happy hacking!
- The Pine64 Star64 Armbian image can now be correctly downloaded.
- The user experience for downloading fetch-restricted files is implemented.
A hint message will be rendered according to the current system locale setting
when such a file is requested.
- pygit2 has been upgraded to 1.5.0 to support libgit2 1.8.
- The
XDG_STATE_HOME environment variable is now correctly respected.
To support devices that require manual intervention during provisioning, and
whose images have to be downloaded manually, the RuyiSDK Device Provisioner is
now being refactored to handle those complex situations, with the next version
expected to be fit for testing. Older versions of the device provisioner will
stop working at that time; please upgrade before you test.
RuyiSDK 0.11 is now released. The corresponding package manager version is also 0.11.
You can download the RuyiSDK package manager from one of the following locations:
This update mainly consists of the following changes. Happy hacking!
- Removed the only LGPL dependency so far. The entirety of RuyiSDK Package
Manager and its dependencies are now permissively licensed, which means
downstream users are free to use the RuyiSDK Package Manager in a
commercial fashion from now on.
- The Ruyi Device Provisioner (
ruyi device provision) now supports the following device models:
Please run ruyi update to pull in the update after upgrading the RuyiSDK
package manager.
We have noticed that more and more device models (even including the newly
announced BananaPi BPI-F3) are having their system images distributed by
means of net-disks only, such as Baidu Netdisk, Google Drive or MEGA.
It is a challenge to support such models due to this; we will attempt to do
so nevertheless in the coming releases. Stay tuned and your contribution is
welcome!
RuyiSDK 0.10 is now released. The corresponding package manager version is also 0.10.
You can download the RuyiSDK package manager from one of the following locations:
This update mainly consists of the following changes. Happy hacking!
- A global command-line option
--porcelain is now supported for external programs to conveniently interact with ruyi. ruyi list and ruyi news list are the first to gain a porcelain output format.
ruyi news list now prefers to present a news item in the system's current language if a translation is available.
RuyiSDK begins to support WinChipHead (WCH) RISC-V products from version 0.10 on.
- The LLVM toolchain maintained by PLCT is now packaged:
toolchain/llvm-plct, whose main feature is support for the XTHeadVector extension.
- The Ruyi Device Provisioner (
ruyi device provision) now supports the following device models:
- WCH CH32V103 EVB
- WCH CH32V203 EVB
- WCH CH32V208 EVB
- WCH CH32V303 EVB
- WCH CH32V305 EVB
- WCH CH32V307 EVB
- WCH CH582F EVB
- WCH CH592X EVB
Please run ruyi update to pull in the update after upgrading the RuyiSDK
package manager.
RuyiSDK 0.9 is now released. The corresponding package manager version is also 0.9.
You can download the RuyiSDK package manager from one of the following locations:
This update mainly consists of the following changes. Happy hacking!
- Unpacking of LZ4-compressed files is now supported.
RuyiSDK supports the entire Sipeed RISC-V product line from version 0.9 on.
The Ruyi Device Provisioner (ruyi device provision) now supports the following device models:
- Sipeed LicheeRV Nano
- Sipeed Lichee Cluster 4A
- Sipeed Lichee Console 4A
- Sipeed Maix-I
- Sipeed Tang Mega 138K Pro
In addition to the following models for whose support is already present:
- Sipeed LicheePi 4A
- Sipeed LicheeRV
Please run ruyi update to pull in the update after upgrading the RuyiSDK
package manager.
For your convenience following bleeding-edge development, the RuyiSDK team
has packaged a bare-metal toolchain targetting the experimental RV64ILP32 ABI.
Because this is a bare-metal toolchain, no sysroot is provided, and multilib
is not enabled: the ABI to use is ilp32d.
Given the following C program:
long long add(long long *a, long long b)
{
return *a + b;
}
void check(int);
void check_sizes(void)
{
check(sizeof(int));
check(sizeof(long));
check(sizeof(long long));
check(sizeof(void *));
}
We can now build object code conforming to the RV64ILP32 ABI with the proper
toolchain package and profile:
$ ruyi update
$ ruyi install gnu-plct-rv64ilp32-elf
$ ruyi venv -t gnu-plct-rv64ilp32-elf --without-sysroot baremetal-rv64ilp32 /tmp/venv
$ source /tmp/venv/bin/ruyi-activate
$ /tmp/venv11/bin/riscv64-plct-elf-gcc -O2 -c -o test.o test.c
Checking that everything works as intended:
$ riscv64-plct-elf-readelf -h test.o | grep 32
Class: ELF32
Flags: 0x25, RVC, X32, double-float ABI
$ riscv64-plct-elf-objdump -dw test.o
test.o: file format elf32-littleriscv
Disassembly of section .text:
00000000 <add>:
0: 6108 ld a0,0(a0)
2: 952e add a0,a0,a1
4: 8082 ret
00000006 <check_sizes>:
6: 3141 addiw sp,sp,-16
8: 4511 li a0,4
a: e406 sd ra,8(sp)
c: 00000097 auipc ra,0x0
10: 000080e7 jalr ra # c <check_sizes+0x6>
14: 4511 li a0,4
16: 00000097 auipc ra,0x0
1a: 000080e7 jalr ra # 16 <check_sizes+0x10>
1e: 4521 li a0,8
20: 00000097 auipc ra,0x0
24: 000080e7 jalr ra # 20 <check_sizes+0x1a>
28: 60a2 ld ra,8(sp)
2a: 4511 li a0,4
2c: 2141 addiw sp,sp,16
2e: 00000317 auipc t1,0x0
32: 00030067 jr t1 # 2e <check_sizes+0x28>
It can thus be shown that the toolchain indeed generates object code with
32-bit pointer width, but also leveraging RV64 capabilities.
Image packages are now available for the following boards.
You can have your device automatically provisioned with the RuyiSDK Device
Provisioning Wizard ruyi device provision. Or you can still manually
install with ruyi install: files will be automatically unpacked or
symlinked to ~/.local/share/ruyi/blobs/<package name>-<version>.
Thank you for supporting RuyiSDK!
The two models are largely compatible from a hardware perspective, but there
are still slight differences that only shows up in the device trees.
board-image/oerv-awol-d1-base: openEuler RISC-V, base systemboard-image/oerv-awol-d1-xfce: openEuler RISC-V, with XFCE GUI
board-image/oerv-starfive-visionfive-base: openEuler RISC-V, base systemboard-image/oerv-starfive-visionfive-xfce: openEuler RISC-V, with XFCE GUI
board-image/oerv-starfive-visionfive2-base: openEuler RISC-V, base systemboard-image/oerv-starfive-visionfive2-xfce: openEuler RISC-V, with XFCE GUI
