This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Recent cygport and cygwin-specific READMEs [Was: Re: GCC-4.7.2-2: Go/No-go?]
- From: Andy Koppe <andy dot koppe at gmail dot com>
- To: cygwin-apps at cygwin dot com
- Date: Sat, 13 Apr 2013 12:39:06 +0100
- Subject: Re: Recent cygport and cygwin-specific READMEs [Was: Re: GCC-4.7.2-2: Go/No-go?]
- References: <51643F10 dot 7000905 at gmail dot com> <87eheixuz8 dot fsf at Rainer dot invalid> <20130410154730 dot GA404 at ednor dot casa dot cgf dot cx> <516599BE dot 7090000 at gmail dot com> <51661EA2 dot 1070801 at users dot sourceforge dot net> <51665212 dot 6050101 at gmail dot com> <51665F0F dot 8040902 at users dot sourceforge dot net> <5166AE89 dot 2050704 at cwilson dot fastmail dot fm> <51673B2E dot 9090602 at users dot sourceforge dot net> <CAHWeT-aCNzjTTq0qa59TPgBRkXo+60Qp13fmPvp7nrThJpbZhg at mail dot gmail dot com> <20130413090322 dot GH11358 at calimero dot vinschen dot de>
On 13 April 2013 10:03, Corinna Vinschen wrote:
> On Apr 13 06:55, Andy Koppe wrote:
>> On 11 April 2013 23:37, Yaakov (Cygwin/X) wrote:
>> > On 2013-04-11 07:37, Charles Wilson wrote:
>> >> #2) Is it possible to use the auto-setup.hint-generator functionality
>> >> for multi-part package sets (e.g. which contain multiple separate
>> >> tarballs, in addition to -src and -debuginfo)? If so, how?
>> >
>> >
>> > Yes; it just works, and also handles inter-subpackage dependencies (e.g.
>> > apps in foo will dep libfooX, and implibs in libfoo-devel will dep the
>> > corresponding DLL in libfooX). Just define CATEGORY/SUMMARY/DESCRIPTION
>> > (there are also subpackage-specific variants of these) and omit the hint
>> > files from $C; at the end of the package stage, cygport will show you the
>> > dependencies it computes for each package so you can check them.
>>
>> I'm struggling to get setup.hint generation to work. Is it supported
>> with cygport 0.11.3 as currently in the distros? Below is the
>> mintty.cygport I've got. Do I need to do anything else to trigger it?
>>
>> Cygport prints ">>> mintty requires:" at the end, which is correct as
>> it doesn't require anything beyond the Cygwin DLL, but there's no
>> setup.hint.
>
> Sure? Did you look into the "dist" subdir in your builddir after
> the install stage? It should contain a complete mintty dir for
> upload.
You're right, there is, inside the working directory created by
cygport, and it looks correct. I'd expected the setup.hint to appear
next to the .cygport and the packaged .tar.bz2 files.
Thanks,
Andy