[swift-corelibs-dev] libdispatch prep for integration to the rest of swift-corelibs
David P Grove
groved at us.ibm.com
Tue Jan 19 12:27:23 CST 2016
Thanks Tony,
I will work on putting something together along those lines (leave dispatch
internals unchanged; optionally invoke its build from build-script)
--dave
From: Tony Parker <anthony.parker at apple.com>
To: David P Grove/Watson/IBM at IBMUS
Cc: Swift Core Libs <swift-corelibs-dev at swift.org>
Date: 01/19/2016 01:11 PM
Subject: Re: [swift-corelibs-dev] libdispatch prep for integration to
the rest of swift-corelibs
Sent by: anthony.parker at apple.com
Hi Dave,
On Jan 19, 2016, at 5:49 AM, David P Grove via swift-corelibs-dev <
swift-corelibs-dev at swift.org> wrote:
I'd like to make progress and push this along.
On Philippe's list of work items from last week were:
> The master build script in swift/utils/build-script needs to be
able to build GCD
> The master build script in swift/utils/build-script to ensure GCD
> and all required components are built before Foundation and the
> appropriate linker paths are passed to Foundation (see how XCTest
is handled)
Currently libdispatch (and libpthread_workqueue) are outliers in that
they use autotools instead of CMake. Do we need to convert dispatch
(and eventually workqueue) to using CMake to get the build system
integration? Or do you want to leave libdispatch using autotools to
drive its build and get swift-build to invoke a more or less
unchanged autotools build for dispatch?
I have time to work on this, but would appreciate some guidance on
what the desired outcome is.
thanks,
--dave
I don’t think using autotools is a barrier to integration into the larger
build script. swift-corelibs-foundation actually builds with a pile of
custom python right now. I think we want to preserve as much of dispatch’s
current build system as possible. The swift/utils/build-script process is
pretty flexible (since it’s a bunch of scripts itself).
Thanks,
- Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-corelibs-dev/attachments/20160119/7e043a1d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <https://lists.swift.org/pipermail/swift-corelibs-dev/attachments/20160119/7e043a1d/attachment.gif>
More information about the swift-corelibs-dev
mailing list