This is a great question, which we should better document, really!
For the Mac frameworks, if you do the install build as in the README:
./Scripts/Build Frameworks install
the resulting frameworks will have @executable_path/../Frameworks in their dyld information. You should be able to link your Mac .app against these by ensuring that the installed products directory where the frameworks ended up is listed in the framework search paths for your app.
Then, after linking, you can then put these in your application's Frameworks directory (Foo.app/Contents/Frameworks) and the @executable_path goo will allow dyld to find the frameworks at runtime.
This is a fairly common pattern for frameworks in standalone Mac apps. We used to install frameworks /Library/Frameworks, but this leads to a form of "DLL hell" where the installed frameworks and dependent apps can get out of sync.