如何获取/构建含全依赖、内置dcraw的跨平台GraphicsMagick静态包？

Hey there! As someone who’s worked with Electron and native binaries before, let’s walk through how to get a fully standalone, static GraphicsMagick build with dcraw support for your app.

Windows Platform #

First, the good news: official GraphicsMagick Windows builds are indeed statically compiled, but we need to confirm dcraw is included. Here’s what to do:

• Download the static x64 (or x86, depending on your Electron target) Windows package from the GraphicsMagick site. Look for packages labeled "static" (they usually have "static" in the filename).
• Extract the zip file to a temporary folder, then open a command prompt and navigate to the bin directory.
• Run gm convert -list format and check if RAW formats like NEF, CR2, or DNG are listed. If they are, dcraw support is built-in. You can also test with a sample RAW file: gm convert your-test-file.nef output.jpg—if it works, you’re good to go.
• Move the entire extracted folder into your Electron project’s resources directory (e.g., resources/gm-windows). When coding, reference the gm.exe path using path.join(process.resourcesPath, 'gm-windows', 'bin', 'gm.exe') to ensure portability.

macOS Platform #

Official macOS builds are often dynamically linked, so we need a static build for full portability. You have two solid options:

Option 1: Compile from Source (Most Reliable) #

• Install build dependencies using Homebrew: brew install dcraw libpng libjpeg-turbo
• Download the latest GraphicsMagick source code.
• Configure the build with static linking and dcraw support:

  ./configure --enable-static --disable-shared --with-dcraw=yes --prefix=/path/to/your/desired/build/folder
  

• Run make && make install—this will generate a static gm binary in the bin folder of your prefix path.
• Test the binary with ./gm convert -list format to confirm RAW support, then move it to your Electron project’s resources/gm-macos folder. Don’t forget to set execution permissions: chmod +x resources/gm-macos/gm.

Option 2: Find Pre-built Static Packages #

If compiling feels too heavy, you can search for community-built static GraphicsMagick binaries for macOS that include dcraw support. Just make sure to verify the binary is fully static (run otool -L gm—if only system frameworks are listed, it’s portable enough for Electron).

Electron Integration Tips #

• Packaging: When using electron-builder, add the GraphicsMagick folders to your package.json under extraResources to ensure they’re included in the packaged app:

  "build": {
    "extraResources": [
      "resources/gm-windows/**/*",
      "resources/gm-macos/**/*"
    ]
  }
  

• Cross-platform Path Handling: In your code, use process.platform to switch between the Windows and macOS binaries:

  const path = require('path');
  let gmPath;
  if (process.platform === 'win32') {
    gmPath = path.join(process.resourcesPath, 'gm-windows', 'bin', 'gm.exe');
  } else if (process.platform === 'darwin') {
    gmPath = path.join(process.resourcesPath, 'gm-macos', 'gm');
  }
  // Use gmPath with child_process or a GM wrapper library
  

• Testing: Always test both in development mode and after packaging to ensure the binary path works correctly and dcraw functionality is intact.

Troubleshooting #

• If the official Windows build lacks dcraw support, compile it yourself using MSYS2/MinGW: install the necessary dependencies, then run the same configure command as macOS (adjusted for Windows paths) to build with dcraw.
• On macOS, if your compiled binary has unexpected dependencies, double-check the configure flags—make sure --disable-shared is set to force static linking.

内容的提问来源于stack exchange，提问作者atwright147