From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Remove libpq.rc, use win32ver.rc for libpq |
Date: | 2020-01-14 21:34:10 |
Message-ID: | 5e471a87-5f90-5e46-acb3-762df64ebebd@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-01-09 10:56, Peter Eisentraut wrote:
> On 2020-01-06 09:02, Michael Paquier wrote:
>> - FILEFLAGSMASK 0x17L
>> + FILEFLAGSMASK VS_FFI_FILEFLAGSMASK
>> Are you sure with the mapping here? I would have thought that
>> VS_FF_DEBUG is not necessary when using release-quality builds, which
>> is something that can be configured with build.pl, and that it would
>> be better to not enforce VS_FF_PRERELEASE all the time.
>
> Note that there is FILEFLAGSMASK and FILEFLAGS. The first is just a
> mask that says which bits in the second are valid. Since both libpq.rc
> and win32ver.rc use FILEFLAGS 0, it doesn't matter what we set
> FILEFLAGSMASK to. But currently libpq.rc uses 0x3fL and win32ver.rc
> uses 0x17L, so in order to unify this sensibly I looked for a
> well-recognized standard value, which led to VS_FFI_FILEFLAGSMASK.
Here is a rebased patch.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Remove-libpq.rc-use-win32ver.rc-for-libpq.patch | text/plain | 11.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2020-01-14 21:45:21 | Re: planner support functions: handle GROUP BY estimates ? |
Previous Message | Tom Lane | 2020-01-14 21:25:00 | Re: Unicode escapes with any backend encoding |