Re: PLUGINS Functionlity in Win32 build scripts - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PLUGINS Functionlity in Win32 build scripts
Date
Msg-id 603c8f070811280542q61ced9fdu5525ebb1234b2bf0@mail.gmail.com
Whole thread Raw
In response to PLUGINS Functionlity in Win32 build scripts  (MUHAMMAD ASIF <anaeem.it@hotmail.com>)
Responses Re: PLUGINS Functionlity in Win32 build scripts  ("Robert Haas" <robertmhaas@gmail.com>)
Re: PLUGINS Functionlity in Win32 build scripts  (MUHAMMAD ASIF <anaeem.it@hotmail.com>)
List pgsql-hackers
On Tue, Sep 9, 2008 at 3:04 AM, MUHAMMAD ASIF <anaeem.it@hotmail.com> wrote:
>      I am currently working in EnterpriseDB (www.enterprisedb.com). During the integration of pldebugger (
http://pgfoundry.org/projects/edb-debugger) with postgres on windows  I faced a problem that plugins are not being
copiedto the lib/plugins directory. Plugins should be copied in (Installation dir)lib/plugins to work properly.
 
>      To solve this problem I added PLUGINS logic in the Windows Perl build scripts of PostgreSQL 8.3.3. It searches
forPLUGINS variable in the contrib Makefile and processes "PLUGINS" as "MODULES" and copies the generated plugin
libraryto the (Installation dir)lib/plugins.
 
> Please find the attached plugin.patch file. Thanks.

Hi,

I've been assigned to review this patch, but I confess I'm a little
murky on what problem it's trying to solve.  Can you explain what I
need to do to recreate the problem?

There's also this comment on the Wiki (not sure why it wasn't posted
to the mailing list...): "Dave Page says: This doesn't work with the
edb-debugger plugin, which is the only such plugin around AFAIK. It
needs to ignore comments on the PLUGINS line, and handle multiple
targets (plugin_debugger, pldbgapi, targetinfo etc). Not sure if we
want that complexity though."  Any comments?

Thanks,

...Robert


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [REVIEW] (was Re: usermap regexp support)
Next
From: "Robert Haas"
Date:
Subject: Re: patch: Add columns via CREATE OR REPLACE VIEW