Charlie Savage wrote:
> Hi everyone,
>
> Thanks for the feedback. The reason for building extensions with MSVC
> on windows is to get access to the Micrsoft debugging tools since as far
> as I can see MingW/GDB cannot debug dynamically loaded dlls on the
> Windows platform (or at least I haven
Hi everyone,
Thanks for the feedback. The reason for building extensions with MSVC
on windows is to get access to the Micrsoft debugging tools since as
far as I can see MingW/GDB cannot debug dynamically loaded dlls on the
Windows platform (or at least I haven't succeeded at doing it).
Anywa
Greg Stark <[EMAIL PROTECTED]> writes:
> Well that sort of stuff is supposed to be covered by the ABI. Consider that if
> it didn't then you wouldn't be able to use any of the standard libraries
> without recompiling them for each compiler since a number of standard library
> APIs depend on structs
Tom Lane <[EMAIL PROTECTED]> writes:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> > The problem here is that the backend is built with mingw but the
> > extension with msvc.
>
> I don't think that it's very reasonable to expect that to work.
> The two compilers very likely have different ru
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> The problem here is that the backend is built with mingw but the
> extension with msvc.
I don't think that it's very reasonable to expect that to work.
The two compilers very likely have different rules for struct
packing, to take just the first gotc
> > Um, is WIN32_CLIENT_ONLY really defined when you're
> building a backend
> > extension? That seems wrong.
>
> Well, it is defined:
>
> #if defined(_MSC_VER) || defined(__BORLANDC__)
> #define WIN32_CLIENT_ONLY
> #endif
Oops. I obviously forgot all about that :-)
> > The
Magnus Hagander wrote:
> > > In pg_config.h:405 this is defined:
> > >
> > > /* Define to 1 if you have the header file. */ #define
> > > HAVE_STRINGS_H 1
> > >
> > > However, Visual Studio 2005 does not include this file. For a
> > > workaround I simply added it but that's a bit of hack.
> >
> > In pg_config.h:405 this is defined:
> >
> > /* Define to 1 if you have the header file. */ #define
> > HAVE_STRINGS_H 1
> >
> > However, Visual Studio 2005 does not include this file. For a
> > workaround I simply added it but that's a bit of hack.
>
> Ah, so even though you are using MS
Charles F. I. Savage wrote:
> Hi everyone,
>
> I've been able to successfully build server extension using Visual
> Studio 2005 for Windows Postgresql 8.1. However, it took a few tweaks
> which I thought I should document (maybe these issues could be fixed in
> future postgresql versions?):
S
Not really. This is for building VC++ extensions that work with
Postgresql for Windows, which is built using MinGW. Thus it allows you
to build extensions with VC++ that work with Postgresql "out-of-the-box"
on the Windows platform.
In contrast, the link below is for rebuilding Postgresql it
"Charlie Savage" <[EMAIL PROTECTED]> wrote
>
> I've been able to successfully build server extension using Visual
> Studio 2005 for Windows Postgresql 8.1. However, it took a few tweaks
> which I thought I should document (maybe these issues could be fixed in
> future postgresql versions?):
>
>
Hmm...this didn't seem to make it to the newsgroup. Apologies if its a
repeat.
Charlie
-
Hi everyone,
I've been able to successfully build server extension using Visual
Studio 2005 for Windows Postgresql 8.1. However, it took a few tweaks
which I thought I should document (maybe
Hi everyone,
I've been able to successfully build server extension using Visual
Studio 2005 for Windows Postgresql 8.1. However, it took a few tweaks
which I thought I should document (maybe these issues could be fixed in
future postgresql versions?):
1. There is no lib file for VC++ to l
13 matches
Mail list logo
