Re: [HACKERS] msvc build broken for ecpg

2007-03-18 Thread Magnus Hagander
>> It's intended to parse as much as possible out of the existing files. >> Unfortunately, the makefiles aren't consistent enough to make this >> always work, which is why each project in /bin/ for example is added >> manually. In /contrib/ they're a lot more consistent, so they're >> auto-parsed.

Re: [HACKERS] msvc build broken for ecpg

2007-03-18 Thread Andrew Dunstan
Magnus Hagander wrote: Perhaps Magnus could give some precise details about the requirements of the buildsystem he's constructed. It's intended to parse as much as possible out of the existing files. Unfortunately, the makefiles aren't consistent enough to make this always work, which is

Re: [HACKERS] msvc build broken for ecpg

2007-03-18 Thread Magnus Hagander
Andrew Dunstan wrote: > > The recent ecpg commit seems to have broken MSVC builds: > > > descriptor.obj : error LNK2019: unresolved external symbol _pg_snprintf > referenced in function _ECPGget_desc > error.obj : error LNK2001: unresolved external symbol _pg_snprintf > misc.obj : error LNK2001:

[HACKERS] msvc build broken for ecpg

2007-03-18 Thread Andrew Dunstan
The recent ecpg commit seems to have broken MSVC builds: descriptor.obj : error LNK2019: unresolved external symbol _pg_snprintf referenced in function _ECPGget_desc error.obj : error LNK2001: unresolved external symbol _pg_snprintf misc.obj : error LNK2001: unresolved external symbol _pg_snp