<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="margin: 0px 0px 0px 6px; line-height: normal; font-family: 'Helvetica Neue';" class="">DYLD_LIBRARY_PATH is not a build-time environment variable.</div><div style="margin: 0px 0px 0px 6px; line-height: normal; font-family: 'Helvetica Neue';" class=""><br class=""></div><div style="margin: 0px 0px 0px 6px; line-height: normal; font-family: 'Helvetica Neue';" class="">I’m writing something up to deal with the need for supplemented library paths, though only in the context of module-map-packages, will this suffice?</div><div style="margin: 0px 0px 0px 6px; line-height: normal; font-family: 'Helvetica Neue';" class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">if DYLD_LIBRARY_PATH is set with custom paths swift will be able to load those .so libraries and execute properly but SPM will not build the swift package unless the .so is in /usr/local/lib</div><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">should spm include those paths while compiling or something other is planned for linking from custom locations?<br clear="all" class=""></div></div></div></blockquote></div><br class=""></body></html>