From 33cb96ba1a84c612491fb5794674a649d1a6a4d6 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 7 Nov 2016 10:19:22 -0500 Subject: Revert "Provide DLLEXPORT markers for C functions via PG_FUNCTION_INFO_V1 macro." This reverts commit c8ead2a3974d3eada145a0e18940150039493cc9. Seems there is no way to do this that doesn't cause MSVC to give warnings, so let's just go back to the way we've been doing it. Discussion: <11843.1478358206@sss.pgh.pa.us> --- doc/src/sgml/xfunc.sgml | 17 ----------------- 1 file changed, 17 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml index 6060e618576..de6a466efc5 100644 --- a/doc/src/sgml/xfunc.sgml +++ b/doc/src/sgml/xfunc.sgml @@ -2577,23 +2577,6 @@ concat_text(PG_FUNCTION_ARGS) error messages to this effect. - - - - To work correctly on Windows, C-language functions need - to be marked with PGDLLEXPORT, unless you use a build - process that marks all global functions that way. In simple cases - this detail will be handled transparently by - the PG_FUNCTION_INFO_V1 macro. However, if you write - explicit external declarations (perhaps in header files), be sure - to write them like this: - -extern PGDLLEXPORT Datum funcname(PG_FUNCTION_ARGS); - - or you'll get compiler complaints when building on Windows. (On - other platforms, the PGDLLEXPORT macro does nothing.) - - -- cgit v1.2.3