[Firebird-devel] boot build *real* success - some questions/thoughts too

[Grzegorz P. <gr...@se...>]

Hi!

I wanted to share with You my recipe for compiling FireBird from source
only. I do the following (after checkouting the source from CVS
interbase module):

Being in interbase dir, having some extra/new versions of files in ..

tar zxvf ../porting.tgz
cp -f ./msgs/msg.gbak ./misc/msg.gbak
cp -f ../iberror.h ./misc/iberror.h
cp -f ../codes.h ./misc/codes.h
cp -f ../isc4.gbak ./misc/isc4.gbak
export NOPROMPT_SETUP=1
./Configure.sh PROD
. ./Configure_SetupEnv.sh
make firebird

And I get "Build succeeded!" message ;-)
It differs from my previous success report, as this time the compilation
is done w/o any other hacks etc.

Anyway - after all those miracles I've seen last days - I will have to
try it more than once to really belive that it works.

Some of You may think that by trying to build from source only I am
making a rode for my own back ;-) No - I am not a masohist ;-)

As it finally works - now I can start writing a helper script that
*really* cleans source dir (so that it looked as You got it from CVS).

Then - there are some questions, for example:

What is "make fireboot" really used for, and why in Makefile's firebird:
target doesn't depend on it, but super-firebird: DOES ?

What's the adventage of having _separate_ boot-kit and NOT using it for
day to day compilations? Why not just have those files in CVS and update
them when needed - no matter how You get them first, but they ARE in
the sources and You have NO _dependency_ on running database and it's
tools (which is WRONG!).
To be honest - it seems sick to me, as it exhibits the loop in source
tree creation, which should be broken/hidden/whatever just not to
distrub people that *just* want to compile the _sources_.

Just my 0.03$, but please consider my words as a fresh mind newcomer.

Will inform You of my progress. If everything goes fine I expect to have
first deb by the end of new week.

					Grzegorz Prokopski