Re: Remove libpq.rc, use win32ver.rc for libpq - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Remove libpq.rc, use win32ver.rc for libpq
Date
Msg-id 5e471a87-5f90-5e46-acb3-762df64ebebd@2ndquadrant.com
Whole thread Raw
In response to Re: Remove libpq.rc, use win32ver.rc for libpq  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Remove libpq.rc, use win32ver.rc for libpq  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unicode escapes with any backend encoding
Next
From: Tomas Vondra
Date:
Subject: Re: planner support functions: handle GROUP BY estimates ?