Re: New release - Mailing list pgsql-odbc

From Dave Page
Subject Re: New release
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4528ADA@ratbert.vale-housing.co.uk
Whole thread Raw
In response to New release  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgsql-odbc

> -----Original Message-----
> From: Joost Kraaijeveld [mailto:J.Kraaijeveld@Askesis.nl]
> Sent: 12 February 2005 10:15
> To: Dave Page
> Subject: RE: [ODBC] New release
>
> Hi Dave,
>
> Attached a makefile (the patch is as big a the makefile) that
> allows VC to both build a release and a debug version.
>
> Changes:
> - Paths to seperate debug output directories are set
> - Added a missing "\" after "$(INTDIR)\win_md5.obj" in the
> debug section

Err, OK - not sure why the patch is so bit (line end problem perhaps? I
committed a fix based on what was originally in there (it must have got
removed in error).

> Question: do we really need the win_md5.c file? It hinders
> compilation with Eclipse "Managed Make Project" and the file
> can be replaced with appropriate -D options.

What's Eclipse? And I'm not sure what D option you mean - cl.exe uses D
for defining macros.

> BTW: the drivers compiles OK with MinGW. Is there any
> interest in a MinGW based Eclipse Project or simple makefile?

I was thinking that we could start building purely in Mingw now that the
backend does. The preferred way would be to use the existing autoconf
build systems (as used on Unix). I haven't had a chance to try yet, but
if you want to, please do.

Regards, Dave.

pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Bug in convert.c copy_and_convert_field
Next
From: "Joost Kraaijeveld"
Date:
Subject: Bug in ODBC driver 08.00.0004 and stored procedure