On Wed, Jun 1, 2016 at 7:17 AM, Karl via swift-dev <swift-dev@swift.org> wrote: > We’d configure it like this: > - SWIFT_HOST_TRIPLE (e.g x86_64-unknown-linux-gnu) > - SWIFT_DEPLOYMENT_TARGETS (e.g. x86_64-unknown-linux-gnu + > armv7-linux-gnueabihf + armv7-none-linux-androideabi + > i386-none-linux-androideabi + …)
Hi Karl, One thing to keep in mind is that triples are not as useful as they can seem to be, and trying to derive information from them can sometimes be a futile exercise because the information just either isn't there, or different vendors mean different things but use the same triple. This is an excellent thread on this topic from llvm-dev: http://comments.gmane.org/gmane.comp.compilers.llvm.devel/87804 Also: https://wiki.debian.org/Multiarch/Tuples#Why_not_use_GNU_triplets.3F I'm not saying that SDK/ARCH is a better replacement (it isn't, it is currently a strict subset of the information from the triple), but at least it is not the triple itself, so people don't have the expectation of being able to provide the triple and let the system figure out the rest. So I'd be concerned about starting to treat the triple as the primary piece of information, and the rest as secondary. 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
