rust-block VS cacao

let block = ConcreteBlock::new(move |key: *const c_char, value: xpc_object_t| { unsafe { xpc_retain(value) }; let str_key = unsafe { CStr::from_ptr(key).to_string_lossy().to_string() }; let xpc_object: XPCObject = value.into(); map_refcell .borrow_mut() .insert(str_key, xpc_object.into()); true }); // https://github.com/SSheldon/rust-block#creating-blocks let block = block.copy(); let ok = unsafe { xpc_dictionary_apply(object.as_ptr(), &*block as *const _ as *mut _) };

This is really specific, but for this point in the article:

> There’s a long guide on Embedding a Command-Line Tool in a Sandboxed App, so I followed that, and then slowly, painfully, factored Xcode out of it, so that I wouldn’t have to figure out how to get a 10GB Xcode install onto the CI machine (remember, you need to be signed in to an Apple ID to download Xcode, and there’s no way to do it from the command-line).

You could actually solve this with Rust and no Xcode whatsoever. cacao [1] and cargo-bundle [2] will produce an app bundle you could sign/notarize/distribute without needing to ever open Xcode.

[1] https://github.com/ryanmcgrath/cacao

I've had basic animation support in cacao for about a year now, but I don't think anybody even realizes it.

But I will reiterate what I say on many posts like these, which is that it would be even cooler if we could stop having a million projects reinvent this wheel - and I say this as someone who wrote a large Rust library that is backed by ObjC. madsmtm has an ongoing effort to put together a best in class ObjC Rust wrapper, which would be great to see even more support for.

MacOS; I have to call the AppKit API. I can use a library like this which offers Rust bindings for AppKit - otherwise I can write my own maybe?

Yes, you can: https://github.com/ryanmcgrath/cacao