On 07/14/2016 08:17 PM, Thomas Mayer wrote:
- I compile these dependencies (and their dependencies) in the
resulting dlls, because there is no user-friendly way to tell users to download the dlls.
hmm. i'm not sure i can follow here. i guess you meant "I link these dependencies statically into the resulting dlls" when you wrote "I compile these dependencies into the resulting dlls", as there is no way to "compile" two binaries together. however, the really unclear thing is whether you actually meant static linking (or not).
also, what is wrong with just putting the dependency dlls *besides* the external (as has been suggested).
- I do not know how to do it in Mac OS X, but as far as I can tell
from pull requests that I have merged, it is more like on Windows than on Linux.
i don't know about your pull requests, but OSX uses the unix way to resolve dependencies (just like linux): the resulting binary (your external) has a notion of where to look for a given dependency, and if that fails it will search the system paths.
see [1] and [2] on how to create an externals that looks for dependencies besides that externals (original code is from hc)
[1] http://gem.iem.at/documentation/faq/how-do-i-make-library-dependencies-local... [2] https://github.com/iem-projects/pd-iem/blob/master/kitchen/pastyroll-osx.sh