Client projects have to include Alamofire.framework even though it’s optional? about siesta

[pcantrell]

Confirmed. Removing all references to Alamofire.framework from the example project’s xcodeproj should work just fine, since Alamofire is an optional dependency and the example project uses the default Siesta’s NSURLSession network. The project does indeed build and launch in this form, but crashes in strange ways that suggest memory clobbering.

This outstrips my understanding of frameworks. I’ll probably just move Networking-Alamofire.swift to another target (but will that confuse poor Carthage?) or another project, but would love it if anyone with a better understanding of frameworks can figure this out.