-
TigaseSwift was not adjusted to beta version of XCode. We will look into that while we will test support for newer XCode - a lot can still change in the next 2 months.
Well, I hope you don't wait for the final iOS14 release, as projects that want to migrate to iOS 14 depend on you. and BTW:
func somename() -> Room { return nil! }
Was that ever legal, or worked it because of a compiler glitch?
-
@vikingosegundo We are in progress of migration from XCode project to SwiftPM (actually SwiftPM project is ready in
mix
branch) which can be directly imported into XCode and is far easier to manage. You should expect XCode project files to be gone soon.If the XCode project file is incomplete (I've not experienced any issues with it) I'm sorry.
-
directly imported into XCode and is far easier to manage
if it compiles. if not, your users are stuck, as they cannot easily change anything.
With other package manger I could still import it as a development package. I have not seen something like this for SwiftPackages.
If the XCode project file is incomplete (I've not experienced any issues with it) I'm sorry.
well, it is. Xcode won't open it. And also I had to force add the project file to the git repository. Although it was not excluded in .gitignore or .git/config/exclude
-
Either way, we are not going to resurrect XCode project (as it was, is and most likely will be problematic) but it will be replaced by SwiftPM really soon and in the next version of SwiftPM, AFAIK, it should be possible to import binary version of frameworks.
Moreover, SwiftPM allows you to generate XCode project file.
I installed tigase-swift via the TigaseSwiftOMEMO package.
In MucModule.swift the line 303
raises the compile time error
I am using Xcode 14 beta 3