Re: [Firebird-odbc-devel] ODBC Driver v.2 Release Candidate 1 is

[eg <eg...@gm...>]

Alexander Potapchenko wrote:
> eg wrote:
>>   
> I agree that it can be necessary and I will include *.lib and *.pdb 
> files into ODBC Firebird driver RC2.

That would be much appreciated.

>>   
> You can use any Firebird header files from official releases. Header 
> files from Firebird 2.1 and VS 2005 are used for ODBC Firebird driver V2 
> build.
> 

The structure of the header file relationships and the build set up 
seems to have changed between FB 2.0  and FB 2.1.1

I just downloaded Fb 2.1.1. sources, and the odbc sources.  I then 
opened the OdbcFB.sln with VS 2005.

I noticed an added include directory named c:\firebird\include in the 
solution. The build.bat file has commnents that you copy over the 
necessary firebird include files such as ibase.h and iberror.h to there 
and build.

I ended up with ib_util.h, perf.h, types_pub.h and then noticed that 
ibase.h is now referring to "../jrd/dsc_pub.h" so of course this doesn't 
quite work.

I am thinking that the solution file 
OdbcJdbc\Builds\MsVc80.win\OdbcFb.sln doesnt quite work out of the box.

Is there a recommended setup for this to build odbcfb properly with 
vs2005 (or 2003 or 2008) and the firebird 2.1.1 source files?

What I did was arrange my source tree as follows:

Fb
|
-- Firebird-2.1.1.17910-0
|
-- OdbcJdbc
|
-- include


The include directory is where I placed the copies of the various 
firebird include files (and I tweaked the solution file to point to it)

To finally get it to work, what I ended up doing instead was to change 
the solution so that it adds additional includes for the various include 
and source subdirectories under \Firebird-2.1.1.17910-0.

The challenge is that the firebird include files seem to be in multiple 
different subdirectories under \Firebird-2.1.1.17910-0.. which I had to 
hunt down.

Specifically, I added the following include subdirectories to the solution:

src\include
src\include\gen
src\jrd


That seems to build (albeit with 182 warnings.. most of which seem to be 
the annoying sprintf / strcpy variety).

If there is another way, please let me know.

If not, perhaps this message will help others build ODBC from the 
sources on windows from the solution file.