[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Qt-Copy checkout problem on windows
From:       Michael Pyne <mpyne () purinchu ! net>
Date:       2009-02-06 19:35:19
Message-ID: 200902061435.28681.mpyne () purinchu ! net
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Friday 06 February 2009, Christian Ehrlicher wrote:
> Thiago Macieira schrieb:
> > Em Sexta-feira 06 Fevereiro 2009, Ã s 08:50:40, Christian Ehrlicher 
escreveu:
> >> Can we remove qt-copy/include until then so we can test 4.5 on windows
> >> or do I have to use the snaphsots from ftp?
> >
> > Do it: svn rm svn+ssh://svn.kde.org/trunk/qt-copy/include
>
> Ok - this breaks in-source builds and because techbase suggest to use
> in-source builds (why?) people on irc complained and won't change to
> out-of-source builds... :-(
>
> To fix this I would like to disallow in-source-builds (why is qt-copy an
> exception to the rule that out-of-source should be prefered?)?

Please let me know where this is at in Techbase so I can change it.  Even 
kdesvn-build (which I used to have code in to simulate out-of-source qt-copy 
builds) has no issues building qt-copy out-of-source.

The only catch is that you should use a -prefix when configuring for later 
installation.

Regards,
 - Michael Pyne

[Attachment #5 (text/html)]

<!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 Friday 06 February 2009, Christian Ehrlicher \
wrote:<br> &gt; Thiago Macieira schrieb:<br>
&gt; &gt; Em Sexta-feira 06 Fevereiro 2009, Ã s 08:50:40, Christian Ehrlicher \
escreveu:<br> &gt; &gt;&gt; Can we remove qt-copy/include until then so we can test \
4.5 on windows<br> &gt; &gt;&gt; or do I have to use the snaphsots from ftp?<br>
&gt; &gt;<br>
&gt; &gt; Do it: svn rm svn+ssh://svn.kde.org/trunk/qt-copy/include<br>
&gt;<br>
&gt; Ok - this breaks in-source builds and because techbase suggest to use<br>
&gt; in-source builds (why?) people on irc complained and won't change to<br>
&gt; out-of-source builds... :-(<br>
&gt;<br>
&gt; To fix this I would like to disallow in-source-builds (why is qt-copy an<br>
&gt; exception to the rule that out-of-source should be prefered?)?<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>Please let me know where this is at in Techbase so I can \
change it.  Even kdesvn-build (which I used to have code in to simulate out-of-source \
qt-copy builds) has no issues building qt-copy out-of-source.<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>The \
only catch is that you should use a -prefix when configuring for later \
installation.<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>


["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic