Branko Čibej

I have the same problem. I built the plugin on macOS (It just needed some love with the dependencies and include paths) and this is what I get from `meson...

I solved the problem on macOS, it was a shared library conflict. See [PR 159](https://github.com/bootchk/resynthesizer/pull/159).

I use this shell script to build the plugin: ``` #!/usr/bin/env bash gimpver=gimp-3.0.4 gimptar=${gimpver}.tar.xz gimpurl=https://download.gimp.org/gimp/v3.0/$gimptar resynth=https://github.com/bootchk/resynthesizer.git srcdir=resynthesizer builddir=resynth-build prefix=/opt/gimp plugins=$prefix/3.0/plug-ins here="$(cd $(dirname "$0") && pwd)" abs_gimpsrc="$here/$gimpver" abs_srcdir="$here/$srcdir" abs_builddir="$here/$builddir" set -e...

When you `#include `, that eventually pulls in headers from all the other packages. Those packages are, in fact if not in intent, part of libgimp's public API. I considered...

> When you #include , that eventually pulls in headers from all the other packages. Those packages are, in fact if not in intent, part of libgimp's public API. In...

So it turns out that even with the recent commit that uses only the include paths from all the dependent packages, I still have to explicitly list all the shared...

To follow up, with this patch I can build a working resynthesizer plugin on macOS. Tested with GIMP 3.0.2 and 3.0.4 on ARM64 (M3 Max). ``` $ otool -L /opt/gimp/3.0/plug-ins/resynthesizer/resynthesizer...

Looks OK now wrt conditionals, since there are no new ones any more. Next time, please don't squash commits before merging; it's impossible to see what changed during review.