[qmtest] running qmtest on bash in cygwin...

[Stefan Seefeld]

Mark Mitchell wrote:
> On Fri, 2003-08-22 at 07:38, Stefan Seefeld wrote:
> 
>>Mark Mitchell wrote:
>>
>>
>>>>just from looking at the GNUMakefile, I see that the version of python
>>>>being used decides also whether to install the qmtest (cygwin shell)
>>>>script or the qmtest.bat batch file. Does this really make sense ?
>>>
>>>
>>>I'm not sure.  We don't want to key off of config.guess output, because
>>>that will always indicate Cygwin, even when using the native Win32
>>>Python.  Ideally, we'd like to get rid of the shell script/batch file
>>>that is used to bootstrap QMTest, but that's another project...
>>
>>well, the generated qmtest.bat file is broken, as the GNUMakefile.in
>>currently hardcodes the (wrong !) paths. Appended is a fix that uses
>>the $(NATPREFIX) instead, consistent with the rest of the Makefile...
> 
> 
> It certainly hardcodes them, but why do you say they are the "wrong"
> paths?  Those are the paths where the Windows package puts QMTest, if I
> recall correctly.

hmm, apparently that was the path for python 1.x.
I installed python 2.2 and it got installed in c:\python22.

> In any case, I think your patch is an improvement.  Older versions of
> Python in combination with older versions of Windows didn't like having
> a space in QM_HOME, but I don't think we need to worry about that now.
> 
> Have you tested your patch?

well, I run 'make install' and then called 'qmtest extensions' which
reported its extensions correctly, so I assume it works.

Hopefully I'll submit a new setup.py script later today as discussed
in another thread so no scripts are needed any more. In case you'd
rather wait...

Regards,
		Stefan