It’s really great when you need to call ObjC APIs from C++ or vice versa.
For the most part you can keep things as regular C++ and then just mix in some ObjC APIs when needed without splitting out your files and targets.
It’s extra useful because macOS provides a lot of really great utility libraries like dealing with media or networking, which means you can greatly reduce your dependency count on Apple platforms.
I try and take the approach of reducing dependencies in favour of platform native APIs where possible when making multi platform code, and this is great for that.
Of course it means you have different details on each platform, but I find it much more pleasant than having to keep building dependencies, and dealing with all the corresponding issues like security, size or dealing with platform specific acceleration.
> I try and take the approach of reducing dependencies in favour of platform native APIs where possible when making multi platform code, and this is great for that.
For the most part you can keep things as regular C++ and then just mix in some ObjC APIs when needed without splitting out your files and targets.
It’s extra useful because macOS provides a lot of really great utility libraries like dealing with media or networking, which means you can greatly reduce your dependency count on Apple platforms.
I try and take the approach of reducing dependencies in favour of platform native APIs where possible when making multi platform code, and this is great for that.
Of course it means you have different details on each platform, but I find it much more pleasant than having to keep building dependencies, and dealing with all the corresponding issues like security, size or dealing with platform specific acceleration.