[itimpi]

Originally Posted by kovidgoyal

The Qt path is not hardcoded anywhere. It is detected from the output of qmake, which should be in your PATH

That is strange - when I run Qmake I get

C:\Calibre>qmake -v
QMake version 2.01a
Using Qt version 4.4.3 in C:\Qt\lib

which is correct - but not what is being used by calibre? It sounds as if it must be getting its values from somewhere else?

I am thinking that the binary version of PyQt that I installed has assumed Qt 4.4.2 as I can see references to it in the file:
C:\Python26\Lib\site-packages\PyQt4\pyqtconfig.py

This item is not too critical as it is easy to work-around using symbolic links. Probably building PyQt4 from source will also correct this problem so I will check that out.

Those include directories are for the windows driver development kit which is need to compile a windows specific module winutil.pyd

I have visual studio 2008 express edition installed and the SDK that comes with it so the include files are at a different location. My point was that the locations are hard-coded into setup.py, so a batch file may be of no use.

You can always create a simple .bat file that sets up the include directories the way they should be on your system, like the bat file used to setup the visual studio command prompt. Once you do that, any extra directories in setup.py will simply have no effect

I am running from a visual studio command prompt that DOES have the directories setup correctly. However the calibre build process did not seem to be using the values from the environment until I altered setup.py appropriately, and then it compiled the winutil.c file without error. I assume you would be happy with me providing a patch to setup.py that reads the values from the environment if they exist?

You should run

python setup.py build_ext

to create the lzx and other C extensions.

I ran that and it worked without errors. However when I later ran
python setup.py build
I still got the errror message about being unable to copy the lzx.so file! Not sure where that message is originating from so that I can correct/workaround it.