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

Photoshop CC 2017 Node.js Extension Building with node-gyp build

New Here ,
Sep 22, 2017 Sep 22, 2017

Alright! So after quite a large chunk of time, my team and I have been able to produce a .node binary that is seen via CEP in Photoshop however we've hit a snag that seems quite dense.

Before we burn even more time on this, I was hoping to draw an answer from someone in the community.

The rundown:

We have a SWIG (Simplified Wrapper and Interface Generator​) wrapper for our tool that compiles a node that Node.js enjoys. The goal is to require("ourApp"); that library much like the examples in the CEP Resources on Github. They have the  The completed build works very well with the native node.exe (matched to the current CC 2017 version 4.3.1). So far so good.

When bringing it into Photoshop we initially received an exception along the lines of "%1 is not a valid Win32 application". That stumped us for a while until we noticed that the bson.node file (within the CEP Resources Example panels) was running 32bit. So, with that in mind, we compiled again with --arch=ia32 and bam! No more error.

This, however, was the beginning of our woes. Instead of that error we now receive the following:

"Error: A dynamic link library (DLL) initialization routine failed."

This, we assume is because of some mismatch of versions, headers, misplaced dependencies, or the lot.

Strictly speaking, Adobe docs state: "Node.js native modules are not directly support since CEP is using a different V8 version from the official node."

Are we missing something trivial or is this all a result of that quote? We would very much like to build and develop tools soon!

[Moved to Photoshop Scripting by Mod]

TOPICS
Actions and scripting
2.2K
Translate
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
Adobe
Community Expert ,
Sep 24, 2017 Sep 24, 2017

Hi,

I see that you've also posted in the Adobe-CEP github repository issues – referencing an old post of mine (see: Are Node addons supported / will CEP ever support them? · Issue #70 · Adobe-CEP/CEP-Resources · GitH...)

For what it's worth, I eventually gave up trying to build "Light Weight Image Processor for NodeJS" as a native module, because I've never found a way to (quoting the response I've been given by former CEP team member) "rebuild the add-on using CEP's version of libuv and v8". My experience with compiling node stuff was, and still is, limited. In case you succeed, please let us know here as well.

Thanks!

Davide Barranca - PS developer and author
www.ps-scripting.com
Translate
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 ,
Sep 15, 2023 Sep 15, 2023
LATEST

@EditShare-Kyra why are you commenting on a 6 year old post?

Translate
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