Skip to content
gweslabPublic

About

Universal Windows CE Emulator - CE Runtime Foundation

Topics

Resources

Contributing

Stars

116 stars

Watchers

7 watching

Forks

Latest commit

 

History

1,497 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Warning

This document covers development and contribution aspects. Visit cerf.cx for user-oriented documentation. This repository includes emulator frontends, website and other tools.

Root repository - UIs and build tools
libCerfEngine - JIT repository; libCerfCore - Emulator repository; cerf.cx - read more information about the project

Discord Patreon

Warning

Beta stage. It is a hobby project, developed in spare time and can't be a called production-grade/exceptionally stable project. Expect bugs, crashes, and breaking changes. CERF stays beta permanently

Downloads

Visit the website to learn how to download a stable or an unstable build.

build

Please read these if you are planning on contributing.

Building

CERF builds on Windows, Linux and macOS with the same build.py script.

Windows

Install modern Visual Studio with the C++ desktop development workload.

Note

The first build on a new machine takes more than one hour. vcpkg compiles the dependencies from source, and build.py builds Qt into third_party/qt/. This occurs one time on each machine. Later builds use the cached trees and are complete in a few minutes. Do not stop the first build.

Linux

Install the build packages. The script installs them with apt, under their Ubuntu 26.04 names:

sudo python3 tools/apt_packages.py linux

Clone vcpkg and run bootstrap-vcpkg.sh in the clone. Set VCPKG_ROOT to the clone. The build downloads Qt into third_party/qt/ and ships it with CERF.

macOS

Install the Xcode Command Line Tools (xcode-select --install) and Homebrew. Then install the build packages:

python3 tools/homebrew_packages.py

All hosts

Caution

Development environment might need additional configuration on your machine that this guide doesn't explain. If you find a bug there, or find a more universal approach - feel free to submit a pull request.

Configure the clone (one time on each machine), then build the entire project with a helper script. On Windows:

python tools/dev_setup.py
python build.py

On Linux and macOS:

python3 tools/dev_setup.py
python3 build.py

tools/dev_setup.py --check is a dry run. The setup will

  • point git at tracked hooks
  • report missing prerequisite

The build script will:

  • wait for a parallel build (Claude Code-special feature for parallel agents work)
  • install a pinned Rust toolchain into third_party/rust and build the resvg SVG renderer
  • build the emulator itself (and will pick appropriate SDK/toolchain from your installations)
  • build all the bundled Windows CE apps (at ce_apps/)

Android

python build.py --android builds build/<Config>/android-arm64/cerf.apk on a Windows or x86-64 Linux host.

python build.py --android=amd64 builds build/<Config>/android-amd64/cerf.apk for an x86_64 Android emulator. Install these first:

  • the Android SDK with the packages that python tools/android_sdk.py --packages prints, and set ANDROID_SDK_ROOT to it
  • a JDK 17 or newer, and set JAVA_HOME to it
  • on Linux, a vcpkg checkout with bootstrap-vcpkg.sh run in it, and set VCPKG_ROOT to it

The build downloads Qt 6.12 for Android and for the host into third_party/qt/.

To sign the package, set QT_ANDROID_KEYSTORE_PATH, QT_ANDROID_KEYSTORE_ALIAS, QT_ANDROID_KEYSTORE_STORE_PASS and QT_ANDROID_KEYSTORE_KEY_PASS.

Building the CE-side binaries (optional)

ce_apps/ holds various Windows CE applications CERF is bundled with including the Guest Additions driver.

You don't need those if you are not working with Guest Additions. You may copy Guest Additions binaries from an artifact or skip them entirely. On x86-64 Linux the build runs these tools through Wine.

macOS and ARM64 Linux cannot run these tools. Give build.py the ce_apps directory of a Windows or x86-64 Linux build, for example from a CI artifact. The build then copies the binaries from that directory:

python3 build.py --ce-apps-from=<the ce_apps directory>

To build ce_apps/, install eMbedded Visual C++ 4.0 (a free Microsoft download from the Microsoft archive). CERF includes a script that will unpack the installation (you dont want and probably can't install ancient tools) and will place the build tools / SDK into appropriate directories. See docs/ce_apps_setup.md.

python tools/dev_setup.py --check reports whether the CE toolchain is present.

Website

This repository includes cerf.cx source code at docs/website.

python tools/build_site.py --serve runs the website on your machine with live reload.

AI Usage / Vibecode Notice

AI-assisted contributions are welcome. That's a nice thing to have in 2026 - you have access to tons of resources right in your pocket. Let me show generic use cases on this project:

  • study emulators, study JIT, study assembly on various archs, study every piece that affects your code that you don't understand how it works yet
  • learn and use AI to reverse engineer; use AI to reach for more correct architecture calls when you stall
  • use AI to find projects/resources with compatible license to learn/borrow something complex
  • use it to find manuals and papers for devices you target, SoCs/peripherals you target and to extract quotes from them
  • use it to work with and explain complex data structures and non trivial algorithms
  • use it to review your code and to criticize it
  • the AI is an instrument to convert plain thoughts into a code - that's a replacement for typing code in order to get the same code you wanted but faster

The vibe code is banned. Please read Contribution Guidelines. Do not turn this into an AI slop. We put an effort here and we maintain a quality level.

Vibecoding non complex modules is fine but you will most likely violate the Contribution Guidelines by producing shitcode.

Claude Development Environment

The environment includes several controversial things you need to know before using it.

  • Full project documentation is injected into a system prompt - this eats tokens
  • The environment kills global clangd.exe and own claude.exe instances if they leak memory
  • Thinking is set to high; bypass permissions mode is set
  • Several own/3rd-party skills included
  • Powerful hooks triggering when agent might do something bad to the codebase
  • IDA MCP is ready to be installed at tools\ida_server.py and tools\ida_claude.py
  • FS Read MCP is a workaround for Read() tool, useful for /tracking restore and massive text files (tools\fs_read_mcp.py)

The environment gives you the /implement-device skill. Run the skill and agent will start the new board bring-up on its own. You need experience - the skill won't do all the work instead of you. (it actually will do, and that's the problem)

Run the environment:

python run_claude.py

CERF was known earlier as WCECL (2019)

CE Runtime Foundation License | Third-Party Notices
Copyright © 2019-2026 Yaroslav Kibysh

About

Universal Windows CE Emulator - CE Runtime Foundation

Topics

Resources

Contributing

Stars

116 stars

Watchers

7 watching

Forks

Releases

Sponsor this project

Packages

Contributors

Languages