Packaging Everything for Testing

Development Core Libraries
1

Howdy,

I have been using the SNAPSHOT .tar.gz to write some basic Swift
applications, and now wanted to turn my attention to compiling with the
latest coming out of the corelibs-foundation library. I understand that to
do so I need to download clang, llvm, swift, and swift-corelibs-foundation
and use the swift/utils/build-script to build everything.

I can do that successfully, but now I have a build/Ninja-ReleaseAssert
directory littered with all manner of artifacts that it's not clear how to
pull together and run with it. Is there either a packaging tool (creating
the filesystem layout seen in the SNAPSHOT) or sets of exports one uses to
run with a hand-built swift and corelibs?

Thanks!
Joe

2

Here's how the official packages are built:

./utils/build-script --preset=buildbot_linux_1404
install_destdir=/tmp/install installable_package=/tmp/swift.tar.gz

Dmitri

ยทยทยท

On Fri, Dec 11, 2015 at 7:13 PM, Joseph Bell via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote:

Howdy,

I have been using the SNAPSHOT .tar.gz to write some basic Swift
applications, and now wanted to turn my attention to compiling with the
latest coming out of the corelibs-foundation library. I understand that to
do so I need to download clang, llvm, swift, and swift-corelibs-foundation
and use the swift/utils/build-script to build everything.

I can do that successfully, but now I have a build/Ninja-ReleaseAssert
directory littered with all manner of artifacts that it's not clear how to
pull together and run with it. Is there either a packaging tool (creating
the filesystem layout seen in the SNAPSHOT) or sets of exports one uses to
run with a hand-built swift and corelibs?

--
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr@gmail.com>*/