Skip to Content.
Sympa Menu

freetds - RE: [freetds] freetds in win32

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'freetds AT lists.ibiblio.org'" <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] freetds in win32
  • Date: Thu, 6 Feb 2003 10:20:34 -0500

This fix is really not the best idea. All this information should be kept
in one place. Maintaining divergent copies of these files for each platform
is not a scalable way to provide good cross-platform portability.

These files were originally written in a manner such that "copy
freetds_sysconfdir.h.in freetds_sysconfdir.h" and "copy
tds_sysdep_public.h.in tds_sysdep_public.h" would be sufficient to configure
these headers for a native WIN32 build. Is MSVC's build system really so
brain dead that it can't handle such a task?

Cheers,
--nick

-----Original Message-----
From: freetds-admin AT lists.ibiblio.org
[mailto:freetds-admin AT lists.ibiblio.org]
Sent: Thursday, February 06, 2003 4:56 AM
To: FreeTDS
Subject: RE: [freetds] freetds in win32


Il gio, 2003-02-06 alle 09:42, Gad Hayisraeli ha scritto:
> yes, but 0.61 still has to be changed in win32 section before release.
> some notes that i had to change manually: 1. error.c is not found in
> the project 2. some ".h.in" ought to be ".h" in order to be found in
> the project 3. missing dll exports

2. fixed. I copied from unix to msvc so files was there


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 we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page