Hi Keith,
Also - the Xcode project is provided for development ease-of-use only. This
version of XCTest is only for non-Darwin platforms, and that builds with the
simple shell script that is in the root directory (build_script.py).
- Tony
> On Jan 4, 2016, at 9:19 AM, Daniel Dunbar via swift-corelibs-dev
> wrote:
>
> I think this makes sense (and commented in your PR). For now we will still
> need the manual build process because we need XCTest to build first in CI, so
> that we can use it in building/testing the package manager itself, but it
> certainly makes sense to shoot for it to just be yet another package.
>
> - Daniel
>
>> On Dec 31, 2015, at 11:42 AM, Keith Smiley via swift-corelibs-dev
>> wrote:
>>
>> Hey all,
>>
>> I was working on integrating a project with corelibs-xctest and I noticed
>> that
>> it doesn't currently support building with swiftpm and instead provides
>> `.xcodeproj` which generates a `.framework`. Is there any future plan to also
>> include a `Package.swift` so that user's could build it either way? Because
>> of
>> how simple corelibs-xctest is this is just a matter of including a barebones
>> `Package.swift` and moving the source files.
>>
>>
>> Thanks!
>>
>> --
>> Keith Smiley
>>
>> ___
>> swift-corelibs-dev mailing list
>> swift-corelibs-dev@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
>
> ___
> swift-corelibs-dev mailing list
> swift-corelibs-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev