# Pitch: Cross-Compilation Destination Bundles

**URL:** <https://forums.swift.org/t/pitch-cross-compilation-destination-bundles/61777>\
**Category:** Pitches\
**Tags:** linux, packagemanager, cross-compilation\
**Created:** [December 2, 2022, 11:24am UTC](https://forums.swift.org/t/pitch-cross-compilation-destination-bundles/61777 "2022-12-02T11:24:16Z")\
**Posts on this page:** 1\
**Showing post:** 47

<div class="post-metadata">

**Author:** ![NeoNacho](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/neonacho/32/1368_2.png) [@NeoNacho](https://forums.swift.org/u/NeoNacho)\
**Post date:** [February 14, 2023, 2:02am UTC](https://forums.swift.org/t/pitch-cross-compilation-destination-bundles/61777/47 "2023-02-14T02:02:39Z")

</div>

> [@Max\_Desiatov](#):
>
> I've updated nomenclature to use "build-time triple" and "run-time triple" instead of "host target" and "target platform", as we think that "target" is too ambiguous in the context of the pitch, especially as it already mentions SwiftPM binary targets multiple times.

I'm a bit late, but I have got to say that I find the new naming extremely confusing since the entire process of cross-compilation is happening at build-time, so either triple is technically a "build-time triple". In fact, the only things running (if we don't take into account testing which the proposal isn't covering) are on the host, so technically the triples used for choosing host tools would be more appropriately named "run-time triples".

---

_[View the full topic](https://forums.swift.org/t/pitch-cross-compilation-destination-bundles/61777)._