If so how should the C++ code be prepared so it’s easily consumed in Obj-C code?
Also is this a valid way of creating cross platform applications if you choose not to use GTK or Qt?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If so how should the C++ code be prepared so it’s easily consumed in Obj-C code?
Also is this a valid way of creating cross platform applications if you choose not to use GTK or Qt?
Yes, we have shipping applications built this way. We have an OS layer (Obj-C on Mac, a Combination of C++, C++/CLI and C# combination on Windows) and a shared portable layer.
One primary concern is to be disciplined in the class definitions so that OS particulars (Obj-C or C++/CLI syntax for example) does not get used in the portable/shared code.
You could create libraries to isolate code but we haven’t needed to do that.