Mail Archives: cygwin-developers/1999/12/04/20:53:55
On Sat, Dec 04, 1999 at 07:48:00PM -0600, Mumit Khan wrote:
>Chris Faylor <cgf AT cygnus DOT com> 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
- Raw text -