[swift-build-dev] importing a *local* native dependency
Drew Crawford
drew at sealedabstract.com
Sat Jan 2 16:42:55 CST 2016
> On Jan 2, 2016, at 3:13 PM, Daniel Dunbar <daniel_dunbar at apple.com> wrote:
>
> 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.
I think this is a very reasonable limitation.
What if we did something like this?
* 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
* Define a particular folder like include/ that we pass as `-I include/` if it exists.
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.
That way the include path is internal to the package sandbox.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-build-dev/attachments/20160102/61f96fbe/attachment.html>
More information about the swift-build-dev
mailing list