Re: Create a shell to get data from SQL Server using FreeTDS

James K. Lowden wrote:
> [email protected] wrote:
>> I try to do this:
>>
>> copy sql.h, sqlext.h and sqltypes.h to /usr/local/include dir
>>
>> ./configure -prefix=mypath -with-odbc-nodm=/usr/local/include
>>
>> And the result is 
>>
>> checking compile-time options
>> configure: error: sql.h not found
> 
> So close!  
> 
> $ ./configure --help | grep nodm
>   --with-odbc-nodm=DIR    build odbc using headers in DIR/include
> 
> You don't specify the include directory; you specify the directory that
> has an include directory.  In your case, /usr/local.  
> 
> It may seem a little odd, but it's not crazy.  The notion is that a normal
> tree has pairs of include and library directories e.g., 
> 
> /usr/include	/usr/local/include	/usr/pkg/include
> /usr/lib	/usr/local/lib		/usr/pkg/lib
> 
> Because a configure script typically needs both, the user provides just
> the parent.  It so happens that --with-odbc-nodm has no use for a lib/
> directory, but the pattern is followed anyway.  

FWIW, most standard GNU configure scripts have options that you may want 
to adopt into the FreeTDS configure script:

--with-xxx=DIR			includes in DIR/include, libs in DIR/lib
--with-xxx-includes=INCDIR	includes in INCDIR
--with-xxx-libraries=LIBDIR	libs in LIBDIR

You can just specify --with-xxx=DIR to set the parent directory of the 
headers and libraries directories, and you can override the default 
DIR/include and DIR/lib via --with-xxx-includes and --with-xxx-libraries.

This would probably eliminate most of the confusion regarding misuse of 
--with-odbc-nodm.

	Cheers,

	-- Johnny C. Lam