FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Daniel Morgan [mailto:danmorg AT sc.rr.com]
> Sent: October 4, 2002 4:19 AM

> What auto* stuff needs be done to get it to build on win32?

Hi Daniel, 

The Alice in Wonderland quality of using the autotools to generate Win32
DLLs is too rich for words.  Almost.  :)

I think you're right that a couple of years ago Brian had FreeTDS working as
a Win32 library, and I also think that the compilier was VC.  

Here's a place to start:

http://sources.redhat.com/autobook/autobook/autobook_242.html#SEC242

"Recent versions of the binutils ... can build binaries which are
independent of the `cygwin1.dll' DLL. [...] Source code designed to be
compiled this way will not compile on Unix however...."

I'm not sure I'd take that at face value, but at the same time I know it's
not a simple matter of throwing this or that switch.  DLLs are more like a
specialized executable than a static library; they need to a provide
specific interface to the OS for initialization (for one thing).  You'll
need to be or become familiar with that sort of thing, because the compiler
can't generate it for you.  

If I understand you correctly, you want to create a (db-lib?) DLL using gcc
on an i386 platform.  Just to be clear, is the host OS Linux (or similar),
or do you plan to use cygwin?  

I got mail from Steve Balmer yesterday, telling me and his million best
friends he wants to get closer to his customers.  If you get this to work,
I'd like very much to reply to him, attaching a link to our documentation.
To let him know how close we are to him, too, don't you see.  

Regards, 

--jkl

P.S.  4:19 AM?  


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.