[qmtest] building from CVS for Windows

[Mark Mitchell]

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 of a week ago, at least, the test classes you mentioned worked fine. 
(Note that a requirement is that you download the Python Win32
extensions; this is documented on our web site, although a note should
also be added to README in CVS.)

-- 
Mark Mitchell <mark at codesourcery.com>
CodeSourcery, LLC