[qmtest] building from CVS for Windows

[Stefan Seefeld]

Mark Mitchell wrote:
> On Fri, 2003-08-29 at 14:22, Danny R. Faught wrote:
> 
>>Anyone have guidance on how to set up a CVS dump of QMTest on Windows?
>>
>>I can get a build under Cygwin, but I can't get a basic 
>>command.ShellCommandTest or command.ExecTest test to run.  Perhaps this 
>>is a known issue, given recent discussions about Cygwin.
>>
>>I tried to do another build in as native a Windows environment as I 
>>could.  I used a native port of gmake.  I didn't have a native shell to 
>>run configure, so I used the Cygwin bash shell, which seems to have 
>>allowed some Cygwin-isms to creep in, such as installing in 
>>/usr/local/bin.  I can build it but I can't run it:
>>
>>C:\temp\qmdb>c:\temp\dosqm\qm\qm\test\qmtest.bat gui
>>c:\Python22\python: can't open file 'C:\progra~1\qmlibqmtestqmtest.py'
>>
>>C:\temp\qmdb>c:\cygwin\usr\local\bin\qmtest gui
>>c:\Python22\python: can't open file 'C:\progra~1\qmlibqmtestqmtest.py'
>>
>>I believe the libraries went to C:\cygwin\usr\local\lib.  Would I have 
>>any more luck if I run configure with a native Windows port of a Unix 
>>shell?  How do you folks build in Windows?
> 
> 
> See scripts/qm-release.  Look for "build_exec".
> 
> We use a native Python, but we use Cygwin to run the build scripts.
> 
> (I haven't tried this in a few days, and there's been a lot of recent
> activity on the build process, so I wouldn't be amazed if something is
> broken just at the moment.)

As I couldn't run qmtest with the cygwin version of python (the 
child-process problems I mentioned earlier), I compiled qmtest with
the win32 python (still from within a cygwin shell). That worked well,
and with my fix to the GNUmakefile.in file it sets up a working
qmtest.bat script.

I run this script from within a windows command line interpreter
successfully.

It would clearly be a good idea to not only set up a batch file,
but a (cygwin) shell script, too, so qmtest could be used from
both environments. Right now the type of script that is generated
depends only on the python executable that is used during the build.


The new build system will hopefully fix this shortly.

Regards,
		Stefan