Just a little update. It is true that other search paths can be easily added
for FIREBIRD_HOME, but it won't make any good in this case, because the
search algorithm is looking for a full Firebird distribution with bin/
include/ and lib/ subdirs in the FIREBIRD_HOME path.
In this case (KUbuntu) the distribution
files seem to be scattered all over the filesystem, so '/usr/lib/firebird/2.x'
won't be recognised as a valid FIREBIRD_HOME path.
But the good news is that, now, all tests pass, thanks to the work made
by the fellow team members of the project all important bugs were fixed.
Regards, Ştefan
Update: Reformulated the post, hope is much clear now :)
| [reply] |
Hi Ştefan,
I forgot to say it's all working now. If I use the -i option and I don't use my own database but let it create it's own test database, everything works fine.
Does your update mean I can use my own database to at installation time?
Regards
Steve
| [reply] |
Hi Steve,
I reformulated the precedent post, hope is much clear now.
It works without the interactive switch in KUbuntu if you set something like this in the bash environment:
export FIREBIRD_HOME=/usr/lib/firebird/2.1
export FIREBIRD_INCLUDE=/usr/include
export FIREBIRD_LIB=/usr/lib
Yes, theoretically you can use your own database, on the local box, but it have to be a TEMPORARY database because WILL BE DROPPED at the end of the tests, so I think, is better to use the one created by the testing system.
Regards, Ştefan | [reply]
[d/l] |
