ZQuestClassic VS sccache

I've been doing some modernization on an old scripting language used by the game engine I work on [1]. Added a garbage collector, simplified how internal symbols are defined, added a VS code extension with some niceties like syntax highlighting, "Go to Definition", and doc tooltips. Also recently added support for websockets and plan to tackle JSON soon.

https://github.com/ZQuestClassic/ZQuestClassic

ZQuest Classic - Engine to play and create games like the original Zelda. C++, OpenGL

Developing a new website for the open source game engine I work on. Nearly finished with it.

https://zquestclassic.com

It's a Zelda-like game engine with some 1000ish games made in it over 20 years. Used to be called Zelda Classic, but we renamed it this year.

Thanks, that was a silly oversight. Your comment is appreciated, as it saved an instruction in my game engine's JIT compilation :)

https://github.com/ArmageddonGames/ZQuestClassic/commit/0a78...

I found Sentry's crash reporting (which uses crashpad) simple enough to configure into an existing CMake build within an afternoon.

Building Sentry/crashpad from source in a few lines of CMake: https://github.com/ArmageddonGames/ZQuestClassic/commit/3471...

And a few lines in the main function: https://github.com/ArmageddonGames/ZQuestClassic/commit/3471...

My hobby is working on a 20+ year game engine. Still occasionally delete DOS-only code in it. https://github.com/ArmageddonGames/ZQuestClassic

```

The `Hero.{x,y}` properties here are a custom fixed precision number class with some implicit conversions to int, which I suspect being relevant to the crash.

[1] https://github.com/ArmageddonGames/ZQuestClassic/blob/e678e9...

https://github.com/ArmageddonGames/ZQuestClassic/commit/641d...

Using it locally too, works great on Mac, but on Windows ccache has some problems caching debug builds. IIRC the embedded debug symbols use absolute paths, so the presence of this particular flag (/Z something...) disables cache eligibility.

i love zelda. if interested in custom quests on pc, go to zeldaclassic.com 100s of custom quests

If you'd like to try custom quests on computer, go to http://zeldaclassic.com

Use icecream or sccache. sccache supports distributed builds.

https://github.com/mozilla/sccache/blob/main/docs/Distribute...

Worth noting that the first commit in sccache git repository was in 2014 (https://github.com/mozilla/sccache/commit/115016e0a83b290dc2...). So I suppose that what "happened" happened waay back.

If you have lots of shared dependencies, maybe try sccache?

I'm going to set up sccache [0] to use it tomorrow. We use MSVC, so EFS is off the cards.

[0] https://github.com/mozilla/sccache/blob/main/docs/S3.md

I think the primary benefit of pre-built procmacros will be for build servers which don't use a persistent cache (like sccache), since they have to compile all dependencies every time. But IMO improved support for persistent caches would be a better investment compared to adding support for pre-built procmacros.

Checkout https://github.com/mozilla/sccache

https://github.com/mozilla/sccache is another option which addresses the use cases of both icecream and ccache (and also supports Rust, and cloud storage of artifacts, if those are useful for you)

That being said a compilation cache, eg the de-facto standard for Rust: sccache (https://github.com/mozilla/sccache) will help to compile and store some of the build artifacts centralized - still for each crate version + build profile (RUSTFLAGS) combination.