Skip to main content
daves95694859
Inspiring
June 22, 2017
Answered

Error loading plugins mac OS

  • June 22, 2017
  • 1 reply
  • 2426 views

Hi

I have been attempting to make a cross platform plugin for Illustrator using the latest Illustrator SDK, which also makes use of the XMPToolkit. I've managed to get builds working and running on Windows, including distributing it to other machines.

On macOS however I'm having a bit of a peculiarity where I have managed to get my builds building but they only work if I run Illustrator by setting the Executable inside the Scheme settings to Illustrator and running it from XCode. In this scenario the plugin loads and works correctly. As soon as I run Illustrator stand alone I get the "Error loading plugins" message. I have tried this with both debug and release builds to no avail. I have also tried some of the sample projects which appear to work. I'm linking the XMPFiles and XMPCore libraries to it so I wonder if it's due to my lack of understanding of frameworks in macOS.

If anyone has any ideas I would greatly appreciate it. Many thanks in advance.

This topic has been closed for replies.
Correct answer LeoTaro

Sounds like it can't find the shared libraries. You should be able to see more useful error messages in the Console log or by running Illustrator from a terminal window.

1 reply

daves95694859
Inspiring
June 22, 2017

I have just tried removing the framework and the static libraries, and removing any dependent code. The plugin now successfully loads. Is this likely to be a build configuration issue?

LeoTaroCorrect answer
Inspiring
June 22, 2017

Sounds like it can't find the shared libraries. You should be able to see more useful error messages in the Console log or by running Illustrator from a terminal window.

daves95694859
Inspiring
June 22, 2017

After running it from terminal, it told me that it couldn't find the framework files. Illustrator was looking inside its own framework folder inside the Package Contents. Manually adding my frameworks to that folder works and now I can run it correctly, so thanks. But, is there a way to get it to use a relative path specified inside the build settings?