public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Brian Ford <ford@vss.fsi.com> To: cygwin-xfree@cygwin.com Subject: RE: non-widget child "DropSiteManager" error (WAS: RE: Grace (xmgrace) 5.1.12-1 ... ) Date: Wed, 21 Jan 2004 16:09:00 -0000 [thread overview] Message-ID: <Pine.GSO.4.58.0401210956370.17483@eos> (raw) In-Reply-To: <972A5A4D5DCE4B4989643A8BF329AD7E091E36@icex34.cc.ic.ac.uk> On Wed, 21 Jan 2004, Atwood, Robert C wrote: > Brian Ford wrote: > >Robert C Atwood wrote: > >> Is this documented somewhere? > >> > >What does *this* mean :^D? > > > :-C > *fulmination removed* > > Umm ... is there a place where it says 'Here is how you build a Cygwin > package from the source archive distributed via Cygwin setup. 1. Unpack > the archive 2. There will be a script called <package><release>.sh 3. > Run this script with (one of) the followign arguments: prep , build, > all, (etc.) 4. Here is what each of the arguments do. ... 5. this > produces an archive, unpack this as follows.... 6. anything else. > Sorry. If you look at the context from your previous message, it really was not clear whether this refered to --[enable|disable]-[static|shared], how to build a DLL with libtool, etc. In fact, the this you explained above was not even on my guess list :). Is think this is the closest this to what you are looking for: http://cygwin.com/setup.html#package_contents Look under "Method 2". > Also I believe the following addition to the script would probably save > some people (like me) much headache ... suitably filled in where blank, > I don't quite get what all the different options are for. > I agree. PTC. Please send them to cygwin-apps at cygwin dot com. Although, don't get your hopes up. There has been another very useful patch to this script pending for a long time now, and it is not clear why it has not been accepted. I'm not sure who is in charge of the generic build script. Maybe that is the problem. [snip] I have my new machine set up now, so I'll try to take a stab at compiling it myself today. I'll let you know how I make out. Thanks for being patient. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
next prev parent reply other threads:[~2004-01-21 16:09 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-21 11:29 Atwood, Robert C 2004-01-21 16:09 ` Brian Ford [this message] 2004-01-21 18:04 ` Igor Pechtchanski 2004-01-22 16:41 ` Brian Ford -- strict thread matches above, loose matches on Subject: below -- 2004-01-21 16:35 Atwood, Robert C 2004-01-21 17:56 ` Christopher Faylor 2004-01-21 15:44 Atwood, Robert C 2004-01-21 12:12 Atwood, Robert C 2004-01-21 12:56 ` David Fraser 2004-01-20 20:21 Atwood, Robert C 2004-01-20 21:59 ` Brian Ford 2004-01-20 19:16 Atwood, Robert C 2004-01-20 22:02 ` Brian Ford 2004-01-20 18:31 Atwood, Robert C 2004-01-20 18:54 ` Brian Ford 2004-01-20 10:48 Atwood, Robert C 2004-01-20 17:23 ` Brian Ford 2004-01-19 18:08 Atwood, Robert C 2004-01-19 22:44 ` Brian Ford
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=Pine.GSO.4.58.0401210956370.17483@eos \ --to=ford@vss.fsi.com \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).