From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Greg Landrum <greg(dot)landrum(at)gmail(dot)com> |
Cc: | pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: writing backend extensions using Visual |
Date: | 2005-03-26 16:25:27 |
Message-ID: | 42458CF7.2050606@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
Greg Landrum wrote:
>On Fri, 25 Mar 2005 17:57:07 -0500, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
>>Greg Landrum <greg(dot)landrum(at)gmail(dot)com> writes:
>>
>>
>>>After playing around for a while, I managed to get a DLL to build and
>>>work at least far enough that I can CREATE and call the functions from
>>>psql. However, it looks like every argument I pass into the functions
>>>comes in as null (e.g. PG_ARGISNULL returns true). This clearly is
>>>less than helpful. :-)
>>>
>>>
>>Sounds like MSVC is interpreting the layout of the FunctionCallInfo
>>struct differently than the MinGW compiler did. You should probably
>>look into whether there are "pragma pack" directives lurking in your
>>program. ("pragma pack" is evil...)
>>
>>
>
>I've got the library stripped down to the bare minimum (just a couple
>of demo functions) and I can't seem to find any uses of pragma pack,
>so I don't think that's it.
>
>
>
>
Do we actually support building backend extensions with anything other
than our standard build environment? I know we support building libpq
using MSVC, but that is for client use. I'm not even mildly surprised
that building a backend extension with MSVC breaks.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Landrum | 2005-03-26 16:39:20 | Re: writing backend extensions using Visual Studio |
Previous Message | Greg Landrum | 2005-03-26 15:58:30 | Re: writing backend extensions using Visual Studio |