Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Bjoern,

2011/12/12 Bjoern Michaelsen <bjoern.michaelsen@canonical.com>:
Hi,

On Sun, Dec 11, 2011 at 03:13:42PM +0100, Andras Timar wrote:
I was hacking on VersionInfo resource of Windows executables and I
noticed that DLLs built with dmake always have this resource, they
include solenv/inc/shlinfo.rc. But DLLs built with gmake does not have
VersionInfo resource by default. Is this normal? Executables are fully
functional without VersionInfo resource, but I think it is useful to
have it, because it contains file version, copyright notice etc. I
would like to ask, if it is by design, or if it is an undesired
omission.

Well, when I started writing gbuild I did not care to much for the Windows
specific resource files. However, support for it has been later added with
the aptly named solenv/gbuild/WinResTarget.mk. Using it to get VersionInfo
everywhere is possible (it is currently used for example in soffice.bin and
vcl), but I have no strong opinion about it.


OK, I thought so, thanks for confirming. Can you maybe explain the
specific example, where I had the bug yesterday, i.e. ucbhelper was
the only gbuildified module that tried to make VersionInfo resource
from shlinfo.rc, but only under MinGW, and even there it was not
linked. If I understood this example, it would help me to understand
the whole concept better.

Thanks,
Andras

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.