# Engine downloads with "bundled FPC" for all platforms, castle-build-ci to easily use CI with our engine, Woodpecker (Codeberg) CI examples and impressions **URL:** \ **Category:** News\ **Created:** [January 18, 2026, 10:25am UTC](https://forum.castle-engine.io/t/engine-downloads-with-bundled-fpc-for-all-platforms-castle-build-ci-to-easily-use-ci-with-our-engine-woodpecker-codeberg-ci-examples-and-impressions/2086 "2026-01-18T10:25:03Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![michalis](https://forum.castle-engine.io/user_avatar/forum.castle-engine.io/michalis/32/3_2.png) [@michalis](https://forum.castle-engine.io/u/michalis)\ **Post date:** [January 18, 2026, 10:25am UTC](https://forum.castle-engine.io/t/engine-downloads-with-bundled-fpc-for-all-platforms-castle-build-ci-to-easily-use-ci-with-our-engine-woodpecker-codeberg-ci-examples-and-impressions/2086/1 "2026-01-18T10:25:03Z")
| [![Open source, integrations with Jenkins, Docker, GitHub Actions, GitLab CI, Codeberg CI / Woodpecker CI](https://forum.castle-engine.io/uploads/default/original/2X/5/5494d178e171ab282b9d8cc7e8868f05080a7834.png)](https://castle-engine.io/wp/wp-content/uploads/2026/01/combined_osi_ci_logos_2.png "Open source, integrations with Jenkins, Docker, GitHub Actions, GitLab CI, Codeberg CI / Woodpecker CI") | We have a number of news related to using [CI (continuous integration) / CD (continuous delivery)](https://castle-engine.io/manual_automatic_builds.php) with our engine. The idea of CI / CD is that you let some automatic process to be performed on your code, usually each time you make a commit / push to the repository. There are a number of useful things you can do this way (e.g. _compile, auto-test, generate docs, release for many platforms_) and a number of ways to go about it. If you don’t use CI yet, we really encourage it! We have a few pages [documenting how to use various CI with our engine](https://castle-engine.io/manual_automatic_builds.php) and in this post, we present some latest additions to our capabilities: 1. We have extended our [castle-fpc](https://github.com/castle-engine/castle-fpc/) repository releases. They provide FPC, for all platforms, in a recommended version to be used together with our engine. They are built using a nice cross-platform script. They are used by other scripts (`castle-build-ci`, engine building), so this is the basis for other improvements mentioned below. 2. As a direct gain from the previous point, our [downloads](https://castle-engine.io/download) now include FPC “bundled” with the _Castle Game Engine_ for absolutely all platforms, including _Raspberry Pi and Pine64 (Linux / Arm and Linux / Aarch64)_ and macs. The goal is to allow [installing](https://castle-engine.io/install) and [building your first application](https://castle-engine.io/build_first) work as out-of-the-box as possible, on all systems, and even for people new to Pascal. 3. _Stay tuned_: This is also a first step toward [making building for web easier](https://castle-engine.io/web). Our [castle-fpc](https://github.com/castle-engine/castle-fpc/) repository includes alternative “unstable” FPC and we want to add there downloadable cross-compilers for the web. We want to allow downloading such “FPC unstable + web tools” from the engine editor GUI easily in the future. The end goal: allow you to _build for web_ while skipping the [complicated “4.1. Installing Prerequisites” section from the web docs](https://castle-engine.io/web#_installing_prerequisites). 4. _Stay tuned_: This is also a first step toward a few [macOS](https://castle-engine.io/macos) improvements… which we actually already did but are now in the “testing” phase 🙂 Stay tuned for a future post about mac improvements, probably next weekend. 5. You can use new [castle-build-ci scripts](https://github.com/castle-engine/castle-build-ci) in your CI (or just your regular system!) to setup FPC, Lazarus and CGE easily. This is an alternative to getting FPC and CGE some other way, e.g. by our [Docker image](https://castle-engine.io/docker). We use it in our own CI runs, the repo [https://github.com/castle-engine/castle-build-ci](https://github.com/castle-engine/castle-build-ci) contains docs (`README.md`) and example usage. We have tested them with [GitHub Actions](https://castle-engine.io/github_actions) and [GitLab CI](https://castle-engine.io/gitlab_ci). 6. [castle-lazarus](https://github.com/castle-engine/castle-lazarus/) (previously `cge-lazarus`) repository has been extended as well: we provide now Lazarus useful on all our platforms, making our builds easier (e.g. to have good Lazarus on macs and _Raspberry Pi_). 7. Lazarus used to build our engine (in the [downloads](https://castle-engine.io/download)) has been upgraded to the latest _Lazarus 4.4_. 8. Last but not least, we got access to [Codeberg CI](https://docs.codeberg.org/ci/), using [Woodpecker CI](https://woodpecker-ci.org/docs/usage/intro) underneath. 9. New and updated documentation: 10. If you’re a devoted fan, you may notice some new icons in the [Open source and friendly to continuous integration section on the main page](https://castle-engine.io/) and in [features](https://castle-engine.io/features) 🙂 Thank you for reading and stay tuned for more posts with practical gains from these “infrastructure” upgrades. ---
**Author:** ![michalis](https://forum.castle-engine.io/user_avatar/forum.castle-engine.io/michalis/32/3_2.png) [@michalis](https://forum.castle-engine.io/u/michalis)\ **Post date:** [January 18, 2026, 12:22pm UTC](https://forum.castle-engine.io/t/engine-downloads-with-bundled-fpc-for-all-platforms-castle-build-ci-to-easily-use-ci-with-our-engine-woodpecker-codeberg-ci-examples-and-impressions/2086/2 "2026-01-18T12:22:01Z")