I've been hacking on scripts to do builds from the command line. Things work well enough now that I think we can run it hands-free for at least the L10N builds.
But there was a major annoyance that I had to hack around: Some of our dependencies, like SWXMLHash and SQLite.swift, are frameworks that have targets for both OS X and iOS. And they try to build both. And that is what our build trips on. Even though we are building an iOS app, it hard fails on those dependencies which try to build and sign the OS X version of the framework they provide. So, to hack around this I have forked SWXMLHash and SQLite.swift and simply removed the OS X targets. Blunt axe solution. This makes our build go, but it is not a long term solution. We need to point the dependencies back to the original repos and make sure we can build without any specific changes. Otherwise we always lag behind with pinned and forked versions. I don't know where to fix this though. I hope we can either find some option or setting in our project or for the xcodebuild tool to work around this. Or that we can provide a patch for those projects to make them more compatible. (Alamofire also has OS X targets and even a watchOS target, but it does not run into these problems, so it may very well be a dependency specific issue) Any help would be appreciated. I'll be happy to explain how to trigger these build errors. S.
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
