i think developers might be interested to know about :
qestion 1 :
How will evolve the sdk on the ios part ,knowing that Swift language is coming and it s pretty impossible to share libray using c++.
sure it is possible to bridge objective c-c header.
Metal shader doesnt follow any open standard and seems to be performant, only a developer can reduce call, i mean i dont believe in magic.
Anyway it s seems perfomant , if it is more performant than the sdk …we are in trouble no?
about swift integration
- Swift cannot bridge C++. Period. You have to work on your headers to be C and C++ clean using #ifdef __cplusplus. Otherwise, Swift’s processor will simply fail to understand what your headers are doing. And this of course means you need C wrappers for your C++ objects to work with them and manipulate them.
- Once you’ve wrapped your C++ objects up with C APIs, then you’ll likely see linker failures. Swift can’t link against C++ by itself. You will need an empty cpp file in your Swift target in order to make it clear to the linker that you need the C++ runtime linked in along with the static lib. If you are using a dylib or Framework, you can avoid this step. It only affects static libraries.