Runtime linking shared libs in unusual places

Hi there,

I’ve forked ofxOpenNI (experimental branch) and am trying to package linux64 binaries for OpenNI2 and NiTE2 so that linux users can easily use the addon w/ the makefile system and I’m SUPER close. I’ve got everything working with global installs of the libraries and in /usr/lib/x86_64-linux-gnu/ and am now trying to migrate from that setup to a more friendly local install where everything is located in ofxOpenNI/lib/openni2 and ofxOpenNI/lib/nite2. I can compile an example just fine, however I’m not sure of the best practice with pointing the runtime linker towards the libraries. If I use ldd to check the shared libraries of my example build I see: =>  (0x00007ffe3199b000)
/home/brannondorsey/Documents/code/of_v0.9.0_linux64_release/addons/ofxOpenNI/libs/nite2/lib/linux64/ (0x00007f443c837000)
/home/brannondorsey/Documents/code/of_v0.9.0_linux64_release/addons/ofxOpenNI/libs/openni2/lib/linux64/ (0x00007f443c5bb000) => /usr/lib/x86_64-linux-gnu/ (0x00007f443c37f000) => /usr/lib/x86_64-linux-gnu/ (0x00007f443c0dc000)

Notice no => in with my libraries. I’ve added the following in my file:

ADDON_LDFLAGS = -Wl,-rpath=../../../addons/ofxOpenNI/libs/openni2/lib/linux64

Which correctly finds the libraries ONLY if I run app relative to the project root (e.g. ./bin/App). What are the best practices for how to link shared libraries that are bundled w/ addons using the Makefile system?