You mean DYLD_INSERT_LIBRARIES. Yes, it is possible to use that (or DYLD_LIBRARY_PATH) to test these before deployting them.
> On Oct 9, 2016, at 03:35, René J.V. Bertin <rjvber...@gmail.com> wrote: > > On Sunday October 09 2016 01:04:39 Jeremy Huddleston Sequoia wrote: > >> That being said, it's technically possible and they should be binary >> compatible. > > Oh, and what about using DYLD_LIBRARY_PRELOAD? Not for systematic use, but > shouldn't it be useful for testing purposes, or for debugging for instance > when your code triggers one of those dynamic_cast errors (cf. > https://llvm.org/svn/llvm-project/libcxxabi/trunk/src/private_typeinfo.cpp)? > > R > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
