I’m cross-compiling a native compiler. That is to say, I’m not building a
cross-compiler in the way we build for Android or iOS: a native compiler with
foreign standard libraries. Both the compiler and stdlib are foreign to the
build machine.
I’d like to produce an installable package (that much is good), and a
standalone package of tests. I’ll have a go at it in the next few days, then
maybe we can add an installable component to produce a test package. I was
pretty disappointed that the “testsuite-tools” component we have basically
links back to the in-tree tests; It’s not really “installable".
Karl
> On 13 May 2016, at 03:40, Dmitri Gribenko <griboz...@gmail.com> wrote:
>
> On Thu, May 12, 2016 at 6:33 PM, Karl Wagner via swift-dev
> <swift-dev@swift.org> wrote:
>> My original idea was a lot simpler - create a script grabbing the specific
>> executables we need (FileCheck, llvm-link, etc) and the tests, package it
>> up, ship it out via ssh and run it on the intended target, piping the output
>> back. I just couldn’t really figure out what the specific dependencies where
>> - the site config seemed to want the entire source and build tree of swift
>> and LLVM, and I don’t want to package all of that stuff up.
>
> Are you building a native compiler or a cross-compiler?
>
> Dmitri
>
> --
> 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 <griboz...@gmail.com>*/
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
