Hi,

This is literary the same issue as the previously resolved #629, but on macOS.

Namely, on my Linux box everything works well, according to the solution from #629. However, on my macOS laptop, the duplicate libiomp issue arises because javacpp's dnnl jar bundles libiomp.dylib and tries to load it, but my system's MKL have already loaded it.

Interestingly, the same setup on Linux has no issues.

I have set up jvm options, and they work on Linux, but seem to be ignored on macOS?
"-Dorg.bytedeco.javacpp.mklml.load=mkl_rt"
"-Dorg.bytedeco.javacpp.pathsfirst=true"

Another hint: when I go into my local maven ropository's javacpp dnnl jar, and butcher it by deleting libiomp.dylib and repackaging it again, this issue disappears.

Any ideas how to approach this?