FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

I don't want to use config.h for this stuff, since config.h won't exist on
manually ported platforms.  Let's see how things settle out in a few days,
it may work out that everything in tds_sysdep_private.h.in can easily be
moved to config.h.in.  But I don't want to lock us into that paradigm until
it's clear that it gives us the required flexibility.

And tds_configs.h is intended only to define the location of the
configuration files...so I want to have system-dependent porting stuff in a
different location.

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Saturday, October 12, 2002 3:52 AM
To: TDS Development Group
Subject: [freetds] RE: tds_config.h.in

Why not put all not distributable info in config.h ?

I added these lines to configure.in (not committed)

freetds_confdir=`echo "$sysconfdir" | sed "s:\\${prefix}:$prefix:"`
freetds_confdir=`echo "$freetds_confdir" | sed
"s:^NONE:$ac_default_prefix:"`
AC_DEFINE_UNQUOTED([FREETDS_SYSCONFDIR], ["$freetds_confdir"],
                   [Configuration path.])

So, config.h, as usual for not private things and tds_configs.h for
public things.

freddy77



---
You are currently subscribed to freetds as: [Nicholas_Castellano AT acml.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')


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.