Rose Docker Build

v0.1.1

Build the ROSE compiler in a Docker container using autotools or CMake. Use when setting up ROSE development environment, building ROSE from source, or troubleshooting ROSE build issues. ROSE requires GCC 7-10 which most modern hosts don't have, so Docker is the recommended approach.

0· 1.3k·0 current·0 all-time
byChunhua Liao@chunhualiao
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the SKILL.md: all instructions, Dockerfiles, and commands are focused on building the ROSE compiler in containers. Required binaries/env/credentials are correctly minimal (none declared), which aligns with an instruction-only, developer-focused build guide.
Instruction Scope
Instructions stay within build/setup scope (git clone, docker build/run, docker exec). Two actionable items to be aware of: the workflow mounts a host source directory into containers (expected for edit-on-host builds) and may download EDG binaries from edg-binaries.rosecompiler.org if not present in the source tree. These are normal for this developer workflow but worth reviewing before running.
Install Mechanism
The skill is instruction-only (no install spec). Dockerfiles in the instructions install packages via apt-get and (for CMake) add Kitware's apt repository by piping a remote key into apt-key add. This is standard for obtaining newer CMake but does involve adding an external apt repo and network fetches inside the image—inspect the Dockerfile and upstream URLs before use.
Credentials
No environment variables, credentials, or config paths are requested by the skill. The SSH-style git clone (git@github.com:...) implies the user must have their own SSH key configured, which is expected for cloning private repos via SSH.
Persistence & Privilege
Skill is instruction-only, has no install actions, and is not set to always:true. It does not request elevated or persistent platform privileges beyond normal Docker usage by the user.
Assessment
This appears to be a coherent, developer-focused Docker build guide. Before running anything: - Inspect the Dockerfiles included in the SKILL.md (they are shown inline) to ensure you are comfortable with the apt packages and added repo. - Be aware the CMake Dockerfile adds Kitware's apt repo by piping a remote key to apt-key add; verify the key URL and consider alternatives if you prefer not to add external repos. - The workflow mounts your local source directory into the container (docker -v); only mount trusted code and check for sensitive files in the directory before mounting. - The git clone uses an SSH URL (git@github.com...), so it will use your SSH keys if you run those steps; ensure you understand which keys are used and whether the repository is public/private. - The build may download EDG binaries from edg-binaries.rosecompiler.org; verify that server if you need to trust its contents. If you prefer, fetch and vet EDG tarballs yourself and place them in the source tree before building. - Run the build steps manually rather than automating unseen commands, and monitor resource usage (compilation is heavy).

Like a lobster shell, security has layers — review code before you run it.

latestvk97fkxgpbenk91dwy9qn7h821d80pj8n

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments