FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

dmarrer AT bci.cl 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.  

> Now I want to create a shell that connect to SQL Server using FreeTDS
> and  write result data in a text file
> 
> How I write this shell? Which libraries I have to use? 

I don't know what you mean by "write a shell".  freebcp will execute a
query and write the results to a file.  So will sqsh.  So will bsqldb. 
Pick your poison. None of them requires ODBC.  

HTH.  

--jkl