Today I tried the MDK with the provided example. This is what I did:
on a Silicon Mac (Mac Studio in my case) the build succeeded, but wiht many deprecated errors and the resulting example.dylib file was not recognized by Magic. I used Xcode 16.1
on my iMac (Intel, with Monterey and Xcode 13.4.1) the build succeeded but with the warning that OpenGL was deprecated and I should switch over to Metal (?)
I copied the build result folder (called Debug) from the iMac to the Mac Studio and pointed the 'Add Additional Folder' to this Debug folder.
the Module appeared under Example.build but showing a rather lengthly folder structure (see screenshot)
if I placed this example.dylib file on its own in a different folder, Magic didn't recognize the module
So it seems possible to develop modules using Xcode but not for Silicon Mac. And is one bound to the folder structure as shown in the screenshot?
Attachments
Screenshot 2024-10-31 at 14.39.52.png (108.06 KiB) Viewed 17657 times
The dylib file should be able to be used by itself without a lengthy folder structure, but it depends very significantly on how you build it. If you dynamically (not statically) link to libraries in a different folder, and then you change the folder structure, you won't be able to load the dylib.
Thanks for the reply. The library (in this case the OpenGL.framework) was statically linked, but I did put the wrong dylib file into the folder I wanted to add to Magic. That was because the build with Xcode yielded two dylib files with the same name, but in different folders, and I picked the wrong one at first.
I know Magic is an Intel program, so it runs under Rosetta on my Silicon Mac. Any chance of a Silicon version?