May 05, 2017 Re: Add targets for release binaries? (1.3+) | ||||
---|---|---|---|---|
| ||||
Posted in reply to kinke | On Friday, 5 May 2017 at 18:49:46 UTC, kinke wrote:
> On Friday, 5 May 2017 at 16:56:57 UTC, Adrian Matoga wrote:
>> It seems that LDC doesn't use the specified triple verbatim, but may modify it, e.g. "arm-linux-gnueabi" becomes "arm--linux-gnueabi".
>
> That 2nd component of the 4-component 'triple' bothers me too. I've only seen the values `pc`, `unknown`, `none` and now, thanks to you ;), even '' for it so far.
It seems that any number of components is accepted as a 'triple', and if there's more than four, some of them are moved from the inside to the back of it. :)
I'd like to have a couple of targets side by side that would all use "arm-linux-gnueabi" (or maybe "arm-tizen-linux-gnueabi"?), but would differ in their sysroot paths.
I could add extra components to the triple to distinguish these targets and it'd work with the current LDC, but it seems a bit hackish to me. What do you think?
|
May 14, 2017 Re: Add targets for release binaries? (1.3+) | ||||
---|---|---|---|---|
| ||||
Posted in reply to kinke | On Friday, 5 May 2017 at 18:49:46 UTC, kinke wrote: > On Friday, 5 May 2017 at 16:56:57 UTC, Adrian Matoga wrote: >> It seems that LDC doesn't use the specified triple verbatim, but may modify it, e.g. "arm-linux-gnueabi" becomes "arm--linux-gnueabi". > > That 2nd component of the 4-component 'triple' bothers me too. I've only seen the values `pc`, `unknown`, `none` and now, thanks to you ;), even '' for it so far. the second component of the triple is the vendor, so hardware-vendor-os/environment[-abi]. but yeah a blank '' is weird. Most OSX triples are $hardware-apple-$os. All the NVPTX triples are $hardware-nvidia-(cuda|opencl). |
Copyright © 1999-2021 by the D Language Foundation