On 7/27/07, <b class="gmail_sendername">Phil Thompson</b> <<a href="mailto:phil@riverbankcomputing.co.uk">phil@riverbankcomputing.co.uk</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wednesday 25 July 2007 10:04 am, Arve Knudsen wrote:<br>> Well I haven't a clue how configure.py uses qmake, so maybe you could check<br>> with the trolls?<br>><br>> Arve<br>><br>> On 7/25/07, Phil Thompson <
<a href="mailto:phil@riverbankcomputing.co.uk">phil@riverbankcomputing.co.uk</a>> wrote:<br>> > On Wednesday 25 July 2007 9:28 am, Arve Knudsen wrote:<br>> > > Is anything being done about this? I can't imagine it'd be too
<br>> > > difficult ...<br>> ><br>> > If the problem is in Makefile.Release then it's a qmake problem.<br>> ><br>> > Phil<br>> ><br>> > > Arve<br>> > ><br>> > > On 7/22/07, Arve Knudsen <
<a href="mailto:arve.knudsen@gmail.com">arve.knudsen@gmail.com</a>> wrote:<br>> > > > I "solved" this problem by configuring PyQt to concatenate source<br>> ><br>> > files<br>> >
<br>> > > > into 8 pieces, so there would be less going on on the command line.<br>> ><br>> > Now I<br>> ><br>> > > > have another problem though. I have installed Python under C:\Program
<br>> > > > Files and not directly under C:\, which doesn't fly with the PyQt<br>> ><br>> > build<br>> ><br>> > > > system. I had to fix the Makefile.Release in the "designer" directory
<br>> > > > since it couldn't cope with the whitespace in Python´s installation<br>> ><br>> > path<br>> ><br>> > > > -- There were two -I directives to gcc: -I"C:\Program" and
<br>> > > > -I"Files\Python25\include", in addition linking failed since the path<br>> ><br>> > to<br>> ><br>> > > > Python´s library directory wasn't quoted ( i.e., -LC:\Program
<br>> > > > Files\Python25\libs).<br><br>I've added some quotes - which might fix it.</blockquote><div><br>Great, appreciated. Haven't tried it yet, but I will later.<br><br>Arve<br></div><br></div><br>