FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

On Wed, 26 Feb 2003, Lowden, James K wrote:

> > From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafoneomnitel.it]
> > Sent: February 26, 2003 12:00 PM
> > > From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
> > > 
> > > Hmm.  That suggests integrating the ODBC and RPM instructions 
> > > into the main
> > > Build and Install sections.  That's a good idea, because -- 
> > > unlike Perl et.
> > > al. -- the ODBC driver manager is part of those tasks.  
> > > 
> > Mmm... checking index again
> > 
> > 2. Build FreeTDS
> > 3. Install FreeTDS
> > 4. Advanced configuration
> > 5. How to get what works with it working
> >   php
> >   ...
> >   odbc
> > Here we shouldn't repeat all steps for building and 
> > installing.... but ODBC
> > need special configuration totally different from other...
> 
> My thinking is that PHP, Perl, etc. all use FreeTDS's .h files and
> libraries, but they don't affect the build/install process.  You build
> FreeTDS, test it, then go on to sqsh or whatever.  
> 
> ODBC OTOH involves choosing a DM and getting its header files before
> ./configure [1].  Someone looking forward to using unixodbc wants to read
> the UG top to bottom, like a cookbook, but the way we have things arranged,
> he can't do that.  To make that possible, we at least have to integrate the
> ODBC instructions in the Build section.  
> 
> I blame Brian.  He started it.  
> 

Oh sure, it's just like at work, blame the last guy! ;-) Part of the 
problem is that the amount of content has expanded somewhat since we 
started, I've been thinking that a how-to style structure might work out 
better.  There would be some dfuplication, but it'd be clearer and quicker 
for the new user.