Hi there! I am using the toolchain with CMake, for examples see the links above. I can’t help you with any other setup but I can give you my insight why:
I couldn’t get SPM working on Mac with any cross-compiling toolchain. The issue was that Mac SPM had some hard coded paths to the internal Mac-only toolchain that ignored any toolchain bin dir etc you gave it, because reasons. I can feel my blood pressure rising just thinking about it. Over the last 3 years I’ve spent months in the deepest imaginable frustration trying to deal with SPM’s idiosyncrasies and shortcomings here.
We had a somewhat non-hacky setup working with SPM 4.x for Android, although that involved manually adding a whole bunch of include paths and module maps to its command line invocation, because SPM itself wouldn’t. That evidently broke at some point on the transition to 5.x because of the issue above. While I’m sure making a patch to fix that issue wouldn’t be too difficult, I am certain that one further issue after another would come up if we did and frankly I’ve had enough of that stress.
With CMake you just tell it when you want built, adding subdirectories if needed for various library deps, and you’re done. the CMake implementation does have its own bugs regarding static linking right now, but they didn’t stop us putting our app into production within a week of moving over
/rant