<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 2, 2016, at 3:13 PM, Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com" class="">daniel_dunbar@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: HelveticaNeue; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">One thing I would rather not do now is support arbitrary things that introduce external dependencies (like custom include paths). If we are going to support external things, I would still like it to be done in a way where everything is done internal to the package's sandbox.</span></div></blockquote></div><br class=""><div class="">I think this is a very reasonable limitation.</div><div class=""><br class=""></div><div class="">What if we did something like this?</div><div class=""><br class=""></div><div class="">* Run a "./preflight" script/executable if it exists. This could call an external build system. Alternatively the path to the preflight script could be specified in Package.swift</div><div class="">* Define a particular folder like include/ that we pass as `-I include/` if it exists.</div><div class=""><br class=""></div><div class="">Then "preflight" can create that folder in some way–whether that is copying header files around or what–and have it be included in the include paths.</div><div class=""><br class=""></div><div class="">That way the include path is internal to the package sandbox.</div></body></html>