• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Loading "external library" get "I/O error" in mac

Participant ,
Apr 06, 2014 Apr 06, 2014

Copy link to clipboard

Copied

Hey everyone,

I just discovered the "external library" in extendscript. So I opened up the "samplelib" example in Xcode 5 and buit it. But, when I tried to run the script, I keep getting the "I/O error" at line "var sampleLib = new ExternalObject("lib:" + libPath);" . I tried to change the "SampleLib.framework" file to readable and writable for every user, but it didn't help.

So, guys, any idea what I've been doing wrong?

Thanks!!!

TOPICS
Scripting

Views

1.1K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Apr 15, 2014 Apr 15, 2014

Copy link to clipboard

Copied

Hi,

Probably your external object framework is not vaild. Check your Xcode project and rebuild it.

Here is working sample image;

スクリーンショット 2014-04-16 11.09.50.png

Ten

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jun 29, 2015 Jun 29, 2015

Copy link to clipboard

Copied

I'm trying to build the sample ExternalObject XCode project that ships with the latest release of Adobe CC, but am getting an error at compile time that states Apple Mach-O Linker (id) Error:  "Undefined symbols for architecture x86_64".  Am I supposed to include something else to get those "symbols"?  Does the sample project only work for 32 bit?

Thanks for your time and help.

—Arie

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Jun 29, 2015 Jun 29, 2015

Copy link to clipboard

Copied

LATEST

Okay, it turned out to be OSX Deployment Target setting under Build Settings > Deployment of the target.  I had to switch to OS X 10.8 for it to work.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines