Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Sat, 4 Dec 1999 20:53:15 -0500 From: Chris Faylor To: Mumit Khan Cc: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: Good suggestion from the Net... Message-ID: <19991204205315.A9841@cygnus.com> Mail-Followup-To: Mumit Khan , cygwin-developers AT sourceware DOT cygnus DOT com References: <19991204200954 DOT A9717 AT cygnus DOT com> <199912050148 DOT TAA01139 AT mercury DOT xraylith DOT wisc DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912050148.TAA01139@mercury.xraylith.wisc.edu>; from khan@nanotech.wisc.edu on Sat, Dec 04, 1999 at 07:48:00PM -0600 On Sat, Dec 04, 1999 at 07:48:00PM -0600, Mumit Khan wrote: >Chris Faylor writes: >> >> I'm confused. How does this differ from mkvers.sh? What kind of >> version information is being looked for that is not already in >> cygwin1.dll? Are you talking about adding something in the version >> fields of the DLL itself? > >Windows installers and various other tools look inside of the file >for version resource, and can use that for example not to overwrite >a newer version and so on. > >You can look at the version resource with the explorer as well (except >for the w95 original, which needed a fix): right click on the dll, >pick properties and then select the version tab (which only exists >if there is a version resource defined). Yup. That's what I was asking. We had intended to add this to the DLL when we first added versioning but I didn't know of any easy way to do this. For some reason, I was under the impression that our tools couldn't add this information to the DLL, otherwise I would have gone this route with mkvers.sh. >> FWIW, the command "grep '%% ' cygwin1.dll" should display all sorts of >> interesting stuff. Adding this to cygcheck is one of those round tuit >> type of things. > >Here's my current copy of cygwin_dll.rc (if you want it, I'll post the >makefile additions as well). I'd like to generate it automatically to >include the build date as well, but we can always pass that from the >Makefile as a macro. As you noted, this would be trivial to build from mkvers.sh, since it is already adding things like build dates and CVS tags to the file. We probably don't even need the strings that mkvers.sh is adding. I think that all of the stuff from the .rc file should be adequate. cgf