<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Consolas'; font-size:11pt; font-weight:400; font-style:normal;">On Monday 22 September 2008, Andreas Pakulat wrote:<br>
> On 22.09.08 14:55:29, Andreas Pakulat wrote:<br>
> > Hi,<br>
> ><br>
> > it seems that since the switch to 4.4.2 in qt-copy its broken unless its<br>
> > installed over an existing copy. At least for me the QtGlobal forwarding<br>
> > header is not installed anymore and this breaks FindQt4.cmake as it<br>
> > relies on that header existing in QT_INSTALLED_HEADERS directory.<br>
><br>
> Please somebody hand me over a brown paper bag :) Apparently<br>
> kdesvn-build does something wrong when copying the source qt-copy into<br>
> the builddir, causing the headers.pri file in the builddir to be wrong.<br>
><br>
> /me digs head first into perl code - eeek :)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>I'll look at it but I think the change in question is that kdesvn-build no longer copies anything over for qt-copy. i.e. it assumes that the configure script can be run in a different build directory than the source directory like with automake and cmake.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>If this isn't actually the case I'll revert that back to the builddir hack.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Regards,<br>
- Michael Pyne</p></body></html>