This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [ITP] cloudabi-toolchain, cloudab-binutils-*
- From: Maurice Bos <m-ou dot se at m-ou dot se>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 29 Mar 2016 22:01:05 +0200
- Subject: Re: [ITP] cloudabi-toolchain, cloudab-binutils-*
- Authentication-results: sourceware.org; auth=none
- References: <CABbCQwuQnhTWK5M-EgP1vhPBckJ37RrEfYC90QgbHShcNZ5LRQ at mail dot gmail dot com> <CABbCQwsknRhfrHSs337O7pVipJGsnj34d5eBK9RfqeZCNp5=vQ at mail dot gmail dot com> <4089EBBF-8605-47CA-984B-527845F7CD27 at etr-usa dot com>
2016-03-29 21:53 GMT+02:00 Warren Young <wyml@etr-usa.com>:
> On Mar 29, 2016, at 12:35 PM, Maurice Bos <m-ou.se@m-ou.se> wrote:
>>
>> The setup.hint files:
>>
>> category: Devel
>> requires: clang cloudabi-binutils-aarch64 cloudabi-binutils-x86_64
>> sdesc: "Toolchain targetting CloudABI"
>> ldesc: "Toolchain targetting CloudABIâ
>
> Why does this package depend on both architecture-specific packages? What if I only want to develop for x86_64, for example?
This is also how these packages are packaged for FreeBSD and Arch
Linux. But I can split them, I don't care much.
>> category: Devel
>> requires: cygwin
>> sdesc: "Binutils targetting aarch64 CloudABI"
>> ldesc: "Binutils targetting aarch64 CloudABIâ
>
> I believe the need for an explicit dependency on cygwin was removed many years ago. A blank ârequiresâ line is perfectly legal.
>
> (If Iâm right about this, I believe Mr. Bos got this idea from the current setup.html page which still shows such examples.)
I used cygport to generate the packages. It did this automatically, it seems.
>
>> sdesc: "Binutils targetting x86_64 CloudABIâ
>
> Thatâs an obsolete spelling of âtargetingâ.
Thanks, updated.