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. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
