Re: Mark all GUC variable as PGDLLIMPORT
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Robert Haas <robertmhaas@gmail.com>, Magnus Hagander <magnus@hagander.net>, Julien Rouhaud <rjuju123@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Tom Lane <tgl@sss.pgh.pa.us>, Chapman Flack <chap@anastigmatix.net>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Bruce Momjian <bruce@momjian.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-26T23:57:36Z
Lists: pgsql-hackers
On Thu, Aug 26, 2021 at 05:10:39PM -0400, Andrew Dunstan wrote: > On 8/26/21 3:57 PM, Robert Haas wrote: >> On Thu, Aug 26, 2021 at 3:42 PM Magnus Hagander <magnus@hagander.net> wrote: >>> Ugly as it is, I wonder if there's a chance we could just process all >>> the headers at install times and inject the PGDLLIMPORT. We know which >>> symvols it is on account of what we're getting in the DEF file. >>> Not saying that's not a very ugly solution, but it might work? I missed the word "install" first here :) >> If it's ugly, that might mean it's a bad idea and we shouldn't do it >> ... but if it can be made not-too-ugly, it would certainly be nice to >> be able to stop worrying about this. > > How is this going to affect msys builds? No gendef there IIRC. I guess > some similar procedure might be possible ... Wouldn't that be needed for cygwin as well? If we go down to enable that for a maximum number of parameters, I would really agree for doing things so as this never gets forgotten for new parameters and we don't have to discuss the matter anymore. With all that in mind, that would mean a new perl script that does the job, callable by both MSVC and normal make builds. But we have nothing that does a manipulation of the installation contents. And couldn't it be a problem if an installation is overwritten, updated or upgradedd, where there may be contents not coming from the in-core build process but from some extension? -- Michael
Commits
-
Remove PGDLLIMPORT marker from __pg_log_level
- 8d3341266508 15.0 landed
-
Mark a few 'bbsink' related functions / variables static.
- b5f44225b833 15.0 landed
-
Add some missing PGDLLIMPORT markings
- 5edeb574285e 15.0 landed
-
Apply PGDLLIMPORT markings broadly.
- 8ec569479fc2 15.0 landed
-
Helper script to apply PGDLLIMPORT markings.
- 80900d469091 15.0 landed
-
Simplify declaring variables exported from libpgcommon and libpgport.
- e04a8059a74c 15.0 cited