Ben Boeckel

What crash do you see at runtime? I see a null deref in libc, but the back trace is garbled :/ .

You can try as well, but unfortunately getting an Android NDK with GDC is non-trivial, but the gunroar docs are a decent outline of my process for it. I'll check...

I `extern` forward declare `rt_init` and `gc_init` and got further calling it before executing any D code. See `src/android/jni/src/android_main.c` in gunroar.

> The only Derelict component whose cmake configs worked for me was DerelictUtil. The others couldn't get through configure, saying they couldn't find DerelictUtil ISTR a similar problem; not sure...

Look at `COMPATIBLE_INTERFACE_BOOL`. I'd set `CMAKE_D_RUNTIME_{STATIC,SHARED}` appropriately based on a target property for the user to set. The target usage requirements logic should take care of it from there.

Ah, I see the sneaky "(see notes)" link beside the build name(?!) in the summary page; so the link I'm looking for *exists*, but is not very discoverable.

I have a set of diffs locally that I need to test.

Selfishly, icons that would be nice to replace the circles I am using: - newspaper/magnifying glass/magazine for "news" - something graph-like for "social" - wrench for "tools" or "code" -...

Things look good overall except that Fastmail's editor creates `TZUNTIL` lines which `dateutil` [doesn't support yet](https://github.com/dateutil/dateutil/issues/1268).

It doesn't crash, but it does halt loading any other `.ics` files from the directory (not just the one that failed).