Re: [Firebird-test] How to make Sean feel like an idiot...

[John B. <bel...@cs...>]

Sean,

On Monday, August 27, 2001, at 12:45 PM, Leyne, Sean wrote:

>
> How to make Sean feel like an idiot in 3 easy steps...

That was not my intent when I committed the new code, but... ;-)

>
> Step 1.	Have Sean download and install Cygwin
> 		(God! this is painfull process -- download 50mb,
> resulting in a 200 MB install!).
>
> 			{Ok, this is done}
>
> Step 2.	Have Sean download the latest TCS sources from SF.
>
> 			{Ok, I've fought that battle before and fell
> relatively confident -- it's done}
>
> Step 3.	Have Sean then try to figure out how to use the Cygwin bash
> shell to run John B's latest testsuite!
> 		(I read Mark's README file -- I would have had better
> luck reading a message from Claudio written in Spanish!)

I think we could arrange that, if you like :-)

>
> 			{Fuck!!!! Somebody just shoot me and but me out
> of my misery!}

The landscape has changed a lot from when Mark wrote the README.  Most 
of it is rubbish now. , especially the part that says what commands to 
run!  Anyway, since I don't have access to a cygwin install someone else 
(maybe Mark?) will have to help me get everything integrated correctly.  
Here is a quick run-down of what needs to be done for unsupported 
platforms:

1.  Export the correct BP.<platform> and ENV.<platform> blobs from the 
tcs platform DB.
2.  Tell tcs.exp where to find all the important utilities:
	isql
	gbak
	gpre
	gdef (I think it is used)
	drop_gdb (huh, whats this you ask?  A c API program included in TCS 
that needs to be compiled on the platform)
3.  Set the environment variables to point to the fb install.  I think 
this is handled in win32 via the registry.
4.  Set the WHERE_* pointers correctly.  There will be differences here 
depending on what server (classic/ss) is being tested.

Each of the above will be different on each platform, so a generic 
method of determining the correct settings is needed.  My current 
thoughts are create an autoconf script to generate a makefile that has 
all the paths, etc. in it.  Then have the makefile pass the info to the 
test scripts via environment variables.  So if you want to run TCS on a 
preexisting install you just have to do a ./configure; make.  We could 
integrate the configure aspect of the tests into the preexisting fb2 
build process in such a way that all fb2 builds can be tested out of the 
build directory without install.  The one exception might be win32, but 
if we put our minds to it I'm sure we can come up with something.

-John