FreeTDS Development Group

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

> 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.  

> >     'FreeTDS:  Client unable to establish connection to 
> > "Servername" on
> > machine "hostname" at address "192.168.1.17" ', or 
> >  
> >     'FreeTDS:  Login to server "Servername" failed for user 
> > "Username" '.  

> Sounds good. 0.61 or 0.62 ?

0.62.  If you succeed and the patch is easy, 0.61.1.  

Absent reported problems rc5 will become 0.61 final in the next day or so.  

--jkl

[1]  I'm going to update the UG to make what I think is an important
suggestion: to separate the sources from the object files.  On my machines,
I have a freetds/build directory.  My build command is, "cd build;
../configure && make && make install; cd -".  Works like a champ.  I never
have to worry about deleting sources by accident, nor rely on "make clean"
to remove object files, and "grep something include/* src/*/*" doesn't
search the binaries.  If anyone thinks this is a bad idea or has run into
problems using a separate build directory, I'd like to hear from you.  




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.