[swift-build-dev] Accessing types in a "parent" module
paulyoungonline at gmail.com
Fri Dec 4 20:34:53 CST 2015
I created https://bugs.swift.org/browse/SR-66.
Thanks for the help!
On Sat, Dec 5, 2015 at 2:09 AM, Max Howell <max.howell at apple.com> wrote:
> We could support this layout. Though it may make it easy to violate the principle of least surprise when moving sources around later in a project's life. So indeed. Should either error or be supported, not half work.
>> On Dec 4, 2015, at 5:51 PM, Daniel Dunbar <daniel_dunbar at apple.com> wrote:
>> This layout should actually just be an error. We currently expect a layout like
>> (two targets)
>> (one target)
>> If you are trying to create a single target with multiple source files in a directory hierarchy, you should move to
>> Can you file a bug to diagnose this (and probably improve docs around it)?
>> - Daniel
>>> On Dec 4, 2015, at 5:48 PM, Paul Young <paulyoungonline at gmail.com> wrote:
>>> Given the following directory structure:
>>> When running `swift build`, types defined in A.swift are considered to be undeclared in B.swift
>>> Is there currently a way to resolve this without moving B.swift into the same directory as A.swift?
>>> swift-build-dev mailing list
>>> swift-build-dev at swift.org
>> swift-build-dev mailing list
>> swift-build-dev at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-build-dev