|
From: David R. <dre...@mo...> - 2002-08-06 08:34:13
|
As far as I can tell, the FileVersion string is not visible or even accessible from anywhere; so we can safely just ignore it (I know, I know -- so why is it there??). The binary FILEVERSION is accessible from installation programs, etc. as well as being visible from the windows explorer (which is why I added the property sheet). As for the strange division into 2 or 4 integers... Beats me. The way it is currently setup the version number is shown as "0.3.1.1".=20 I cleaned the resource file up a bit (threw away extra junk). I also did some tests with adding extra fields and they seem to work just fine, despite MS's mention of "predefined names". On the property sheet, the description and copywrite as well as the first entry (alphabetically) are immediately visible, the rest have to be selected to be seen. Also, the description and copywrite should be short enough to fit on 1 line (otherwise they need to be scrolled). I'll send you a jpg off list. Thanks for the autoconf/automake pointers. Regards, David Resnick MobileSpear Inc. -----Original Message----- From: David Resnick=20 Sent: Tuesday, August 06, 2002 08:27 To: 'Bastiaan Bakker' Cc: log...@li... Subject: RE: [Log4cpp-devel] Version property sheet added to DLL There is a a description of the VERSIONINFO resource here: http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/tools/= r c_7x2d.asp The file version is in 4 separate entities in the binary format (FILEVERSION). From the docs: Specifies the binary version number for the file. The version consists of two 32-bit integers, defined by four 16-bit integers. Could you please explain to me in a couple of words how template strings (like @PACKAGE_VERSION@) are replaced (what tools are used, a sample command line for doing it, where the replacement values come from)? How do I generate the doxygen config file for example? I used this project's VERSIONINFO as a base for the values I put in log4cpp: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dqsd/dqsd/src/DQSDTools/D QSDTools.rc?rev=3D1.24&content-type=3Dtext/vnd.viewcvs-markup Sorry for dunking you in the doubly cold waters of lawyers and Microsoft ;-). Regards, David Resnick MobileSpear Inc. -----Original Message----- From: Bastiaan Bakker [mailto:bas...@li...]=20 Sent: Monday, August 05, 2002 23:43 To: David Resnick Cc: log...@li... Subject: Re: [Log4cpp-devel] Version property sheet added to DLL On Mon, 2002-08-05 at 08:45, David Resnick wrote: > Hello, >=20 > I've added a "version" property sheet to the DLL version of log4cpp. >=20 > Bastiaan, please check the values in msvc6\log4cppDLL\log4cppDLL.rc. > There are "legalese" type fields there that I filled in with what=20 > seemed to be correct values, but it is hard to tell... >=20 Indeed it is. Is a definition of it's file format available somewhere?=20 Does the file version need to be three separate intities? It would be convienent to template the file with @PACKAGE_VERSION@ in order to keep the version number up to date. Also it would be nice to put the copyright holders somewhere, since LifeLine and me aren't the only ones. Maybe it's easiest to refer to the (informal) 'the Log4cpp Project', but I not familiar enough with this "legalese" stuff to know whether that's OK. But I guess this can simply be added to the "LegalCopyright" field? Anyway the LGPL is the definitive copyright statement for log4cpp...=20 Thanks, Bastiaan =20 =20 =20 > Regards, >=20 > David Resnick > MobileSpear Inc. >=20 >=20 > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf=20 > _______________________________________________ > Log4cpp-devel mailing list Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cpp-devel |