[qmtest] [PATCH] Fix open_temporary_file_fd

[Mark Mitchell]

Andrew Funk wrote:

> Hi Mark,
> 
> This brings up a number of questions for me, so I will try to be
> organized:
> 
> 1. How would I do a ./configure; make; make install with the target
> being the C:\Python23\Lib\site-packages directory (if that's what you
> mean)?  When I set the prefix under Linux to say /home/afunk/qm, it will
> install to /home/afunk/qm/lib/python2.3/site-packages.  So it seems the
> directory structures are different.

Yes.  The Windows installer generated by Python's distutils does use a 
different directory layout.  It's not possible to replicate that with

   ./configure --prefix=...

You'd have to look at how distutils work to duplicate that.

You should be able to use the --prefix= approach on Windows, though; 
you'll just end up with a slightly different layout.

> 2. If I go with option 2, where is the Windows-installer binary created?
> I ran the script but then didn't know what to do next.

It is in the 'dist/' subdirectory.  Look for the .exe file.

> 3. I wanted to try reinstalling the stable release under Windows, so I
> deleted what I thought were all the relevant folders under the
> C:\Python23 directory, then re-ran the installation file.  It created
> the qm tree under site-packages, but didn't put anything in the Scripts
> directory this time..?  

It's possible that you confused it by manually removing the files rather 
than by going through the Control Panel to Add/Remove Programs.

There should be a Scripts\qmtest.py file when the new version is 
installed, but if not that might represent some kind of packaging 
problem.  I'll look into that.

> 4. As an alternative to building under Windows, I have my Linux
> directories mounted under Windows, so I wonder if I could somehow point
> the Windows qmtest.py script to use the Linux installation under
> /home/afunk/qm/lib/python2.3/site-packages?

You might be able to do that, indeed.  I'm not sure how well that might 
work.  You could also try just using the "qmtest" script that is 
installed on the GNU/Linux side.  There may be directory assumptions 
built into the code that are different for Windows vs. UNIX-like 
systems, but if there are, we might want to eliminate them.

Thanks,

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