We had a great dive this morning. Down to 80m to check an ancient ram that’s been sitting on the sea floor since the battle on 10 March 241 BC.
Home for the next couple of weeks, while we document the Battle of Egadi site off Favignana.
Today we say ciao Lipari, and head to Favignana.
We had our final dive in Capistello Bay this morning, finishing some survey measurements. Now we’re all packed for Favignana tomorrow.
Beautiful weather and calm seas for a few dives surveying the Capistello Bay wreck. We cleaned up some points and added a couple of ancient Roman anchors to the survey.
On my way back to Lipari and Favignana to dive Capistello Bay and The Battle of Egadi site for GUE and the Soprintendenza del Mare of Sicily.
Some information on the connection between PFO and IEDCS.
A topic close to my heart…
use_frameworks! from your
If you’ve arrived here you probably have a
Podfile that includes multiple targets for multiple platforms that share some pods, while using the new Xcode build system.
And you’re almost certainly ready to burn everything to the ground.
Thankfully, I already did that, and out of the ashes a solution emerged, resplendent and angry.
There are a couple of issues:
- Xcode is non deterministic with respect to this issue, and will randomly decide whether there is an issue to worry about at all. This is fucking infuriating.
The new build system (randomly, see 1!) doesn’t like duplicate things, whereas the legacy build system didn’t care.
When Swift was introduced, it didn’t support static libraries, so we all dutifully added
Podfiles. When you have multiple platforms sharing pods, you will have multiple copies of the pod source in your
Pods/Target Support Files/folder, and Xcode will get its knickers in a bunch. Sometimes.
Swift now supports static libraries.
use_frameworks!and everything will work.
Peter Mayhew helped define my life, growing up. Even as an adult I’ve never once looked at Chewie and thought: “That’s a dude in a suit”. Not once.