This is the mail archive of the cygwin-apps mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Recent cygport and cygwin-specific READMEs [Was: Re: GCC-4.7.2-2: Go/No-go?]

On 13/04/2013 15:49, Corinna Vinschen wrote:
> On Apr 13 12:39, Andy Koppe wrote:
>> On 13 April 2013 10:03, Corinna Vinschen wrote:
>>> On Apr 13 06:55, Andy Koppe wrote:
>>>> 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.
> IIU Yaakov C, the dist dir is the way to go in future.  The toplevel
> files is the old style, supposed to go away at one point.  I like the
> dist dir approach a lot.

  Glad to hear that.  I also much prefer the dist dir to plonking all the
files in the toplevel with no directory structure.  It's much simpler for


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]