"Igal @ Lucee.org" writes:
> So now I am getting the errors below. Do I need to add an entry in
> _deffile_ for each error message? What does the entry look like?
These look like you're failing to link to whatever library supplies
dbbind() etc. Can't help you more than that.
On 11/2/2017 8:40 AM, Tom Lane wrote:
It looks to me like MSVC is complaining about the PGDLLEXPORT
markings that tds_fdw.c has on the function definitions
(not the extern declarations). In the core code we only put
PGDLLEXPORT in extern declarations ... so try keeping it in
the externs and remo
"Igal @ Lucee.org" writes:
> Any other ideas?
It looks to me like MSVC is complaining about the PGDLLEXPORT
markings that tds_fdw.c has on the function definitions
(not the extern declarations). In the core code we only put
PGDLLEXPORT in extern declarations ... so try keeping it in
the externs
On 11/2/2017 1:05 AM, Laurenz Albe wrote:
Igal @ Lucee.org wrote:
After reading Craig's excellent blog post at
https://blog.2ndquadrant.com/compiling-postgresql-extensions-visual-studio-windows/
I decided to try and build a real extension - tds_fdw.
I've set it up in Visual Studio Community 20
Igal @ Lucee.org wrote:
> After reading Craig's excellent blog post at
> https://blog.2ndquadrant.com/compiling-postgresql-extensions-visual-studio-windows/
> I decided to try and build a real extension - tds_fdw.
> I've set it up in Visual Studio Community 2017, but am getting the following
> e
Hello,
After reading Craig's excellent blog post at
https://blog.2ndquadrant.com/compiling-postgresql-extensions-visual-studio-windows/
I decided to try and build a real extension - tds_fdw.
I've set it up in Visual Studio Community 2017, but am getting the
following errors:
Error C2375
