B4i - working on refactoring the build chain

[Erel]

Up until now, B4i mainly relied on static libraries (.a files). This was the standard packaging when B4i was first released. Since then, Apple has introduced frameworks and xcframeworks, which are more powerful and flexible. In the next version, all B4i native libraries, including libraries compiled by the IDE, will be packaged as xcframeworks. The immediate benefit is support for iOS 26 simulators running on Arm64 Macs.
After going through quite a few hurdles, the main functionallity works now. The next step is to improve support for Swift libraries.

 

[Jmu5667]

No small Task !

 

[JordiCP]

Great news!
Will it keep compatibility with custom-made .a libraries?

 

[mcqueccu]

As always, the community is grateful for all your efforts

 

[Erel]

Will it keep compatibility with custom-made .a libraries?

Yes, you might need to make a small change to the header file. And please test it when the beta is released.

 

[LWGShane]

Awesome to see not only continued updates but also modernizations as well. The support and updates is the biggest reason why I continue to use B4X.

Will there be any other benefits to refactoring the build chain? Or is that still classified?