Super, thank you Scott. That's just what I needed. Have a great day.

Hi Quinn, Thank you for your, expanded, explanation. As I have never done any objective-c or objective-c++, are you able to point me to some examples which will help me write this wrapper, please ?

Hi Quinn, Thank you for all your (painfull) efforts ;-) I have managed to write the wrapper and catch exceptions correctly. Great work, thanks

Ok, I have got a bit further. The define is indeed present and the preprocessor skips over the 64bit calls I want to avoid for the simulator/preview. It is now falling over the inclusion of 64bit static libraries which need to be linked with the application, but are not needed when previewing the UI from within Xcode and SwiftUI. Is it possible to have "conditional" linking ? By that I mean, if we are building for arm64, link the libraries in, otherwise ignore them.

This is not an issue any more, sorry for the unnecessary question. When I refresh the preview, all compiles ok and the libraries are ignored. Shame that I cannot delete this question ...

Hi Scott, Thanks for your reply. I have tried both creating a C++ file and an Objective-C++ file as you proposed. In both of these, XCode complains that it cannot find the class stringor even the header (obj-c++) <string>. Just for to remind you, I am having to use XCode 12.2 and not 14.5 due to system constraints. Any ideas ?

To answer my own question - Yes, I was missing something ! :-( One of those stupid bugs that you go over being persuaded that there is nothing wrong. I was trying to do a to_string on a pointer to an int without dereferencing it - as I said, stupid. Sorry for the bother.

Ah sorry, I forgot to add the script I mentioned, but, when trying to include it here, it ended up as a mess. I simply used the same python script commands as described in the aforementioned article.

So I searched further and found that, during the process of conversion, I could obtain the spec object spec = model.get_spec(). I then dumped this out to a file and saw specificationVersion: 6. So, is this a bug in the version 5.0b5 of CoreML tools ?

@robnotyou, I am sorry that you felt I was being rude, that was not my intention. I can already create the stamp in swift, that's not a problem - its using it to create a continuous "line" of stamps. @OOPer, my question stated that I am using swift a couple of times and I gave the equivalent code in java to illustrate my need - thought that was sufficient info.