Problem defining nix package for igir 3.0.1

[docbobo]

Is your feature request related to a problem?

Yes - coming up with a nix package definition that will work on all platforms.

Describe the solution you'd like

Instead of using homebrew, I am using nix to manage packages installed on my MacOS systems. As it turns out, there is a nix package definition that would install 2.11.0 for linux systems, but it does not support Darwin as a target.

I set out to update that nix definition to a) support Darwin and b) upgrade igir to 3.0.1, but I am currently struggling with chdman and maxcso:

Due to the way that nix operates, path-based dependencies to dynamic libraries need to be updated via patchelf (linux) or install_name_tool (MacOS). This helps retargeting dependencies to e.g. /opt/homebrew/opt/lz4/lib/liblz4.1.dylibto the corresponding library in the local nix store. This works well for all the binary components that I've found to be part of igir: lza, chdman, and maxcso.

It also seems to work well for Linux build. However, for some reason unknown to me, the Linux build does not contain the module that contains maxcso, while the Darwin build does:

Linux (arm64)

$ find ./lib/node_modules/igir/node_modules/@emmercm
./lib/node_modules/igir/node_modules/@emmercm/
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64/README.md
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64/package.json
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64/dist
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64/dist/index.js.map
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64/dist/index.js
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64/dist/index.d.ts
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64/chdman
./lib/node_modules/igir/node_modules/@emmercm/chdman-linux-arm64/LICENSE

Darwin (arm64)

$ find ./lib/node_modules/igir/node_modules/@emmercm
./lib/node_modules/igir/node_modules/@emmercm
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64/LICENSE
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64/dist
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64/dist/maxcso
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64/dist/index.js
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64/dist/index.js.map
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64/dist/index.d.ts
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64/README.md
./lib/node_modules/igir/node_modules/@emmercm/maxcso-darwin-arm64/package.json
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64/LICENSE
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64/dist
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64/dist/index.js
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64/dist/index.js.map
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64/dist/index.d.ts
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64/chdman
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64/README.md
./lib/node_modules/igir/node_modules/@emmercm/chdman-darwin-arm64/package.json

Initially, I thought this might be related to emmercm/homebrew-igir#22 though I am not so sure anymore. Anyway...

I've already tried a few things, but given that my understanding of the NodeJS eco-system is rather limited, I a) have no idea what's causing this and thus b) not the slightest idea how to fix it.

Does anything come to mind there?

Additional context

No response

[docbobo]

It's just the absence of the maxcso binary after build that I need to solve in order to finalize the nix package update.

[docbobo]

I am wondering if that might actually be an Linux/arm64 issue...

[docbobo]

The only obvious difference between chdman-js and macxso-js seems to be that chdman-js also contains a package called chdman-linux-arm while maxcso-js does not have any package for -arm. But I would've expected the arm64 package to be used in either case...

[docbobo]

Lovely - just noticed that this got fixed in maxcso-js v0.1130.8, while v3.0.1 included v0.1130.7..

[docbobo]

@emmercm any chance, we can get a 3.0.2 tag for ec6c184?