Skip site navigation (1) Skip section navigation (2)

Re: psql compiled with msys

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>,<pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: psql compiled with msys
Date: 2004-04-16 12:59:08
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34B769@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
> Right now, psql does not allow copy & paste from the console 
> window when it is compiled under mingw.  However, the psql 
> compiled with the makefile for visual studio does.  Copy & 
> Paste are enormously useful... This may have to do with how 
> the console window is constructed.

Probably. Definitly worth looking into :-)


> On another note, what is the future of the libpq makefile 
> (win32.mak) in src/interfaces?  if the wrong libpq.dll is 
> resolved by psql, it will crash psql...perhaps it should be 
> removed or renamed msvc.mak (there is a bcc32.mak for Borland also).

Hmm. This sounds exactly like the problem Dann (IIRC) had a couple of
days back.

Since they are not compatible, we need to either find a way to make them
;-), or we should probably have two different libpq.dll:s - one for each
binary format. If they can't be made compatible, we *must* provide both
versions. If we can make them compatible, and everything is supported on
ming as is on msvc, we could just drop the msvc build stuff, IMHO.

Anybody know of a way to make mingw produce MS compatible DLLs?


//Magnus

pgsql-hackers-win32 by date

Next:From: Merlin MoncureDate: 2004-04-16 13:29:51
Subject: Re: psql compiled with msys
Previous:From: Bruce MomjianDate: 2004-04-16 12:57:09
Subject: Re: crash on bad database connect

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group