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

List:       kde-windows
Subject:    Re: Review Request: cannot compile qt if kderoot path is too long
From:       "Ralf Habacker" <ralf.habacker () freenet ! de>
Date:       2011-02-15 0:17:09
Message-ID: 20110215001709.8178.69134 () vidsolbach ! de
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


> On Feb. 14, 2011, 3:24 p.m., Wolfgang Rohdewald wrote:
> > now I actually found a note in the wiki about a short path option in kdesettings.
> > 
> > but I lost too much time with this - I do want to make sure this does never \
> > happen again.

emerge provides two strategies in thia area: 

1. path substition by drive letters, which has to be configured in kdesettings.bat \
(you already refered to this)  2. short path usage - replace pathes by the short \
form. This feature is currently package based and could be activated by setting \
self.subinfo.options.useShortPathes -  see EmergeBase.__adjustPath() and where is is \
used for more details.  both strategies could be used together 

There are several limits in this area - nmake, mingw32-make, cmake, command line, \
each one has its own different limit

I found some related thread: 

http://lists.kde.org/?l=kde-windows&m=125717156605667&w=2
http://www.cmake.org/pipermail/cmake/2008-August/023279.html
http://lists.kde.org/?l=kde-windows&m=124222975100566&w=2

> From my personal experience does mingw builds have more problems as msvc builds and \
> the most annoying package is qt 

Ralf 


- Ralf


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6483/#review9838
-----------------------------------------------------------


On Feb. 14, 2011, 3:18 p.m., Wolfgang Rohdewald wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://svn.reviewboard.kde.org/r/6483/
> -----------------------------------------------------------
> 
> (Updated Feb. 14, 2011, 3:18 p.m.)
> 
> 
> Review request for kde-windows.
> 
> 
> Summary
> -------
> 
> On windows, gcc/g++ only take a maximum of 8192 chars for command line arguments. \
> If they get more they will not complain but strange things will happen like \
> compiler segfaulting or gcc misinterpreting the arguments at around position 8192. \
> I did not report this as a gcc bug, maybe somebody else already is registered \
> wherever that can be done. I was using mingw4. 
> So emerge.py now first checks - it allows a maximum of 10 chars like in c:\kderoot. \
> This results in command line lengths up to around 7700 (maybe more, this is what I \
> saw). 
> I was using kderootsvn which makes gcc die when compiling \
> c:\kderootsvn\download\svn-src\qt\src\3rdparty\sqlite\sqlite3.c, the command line \
> having a length of 8214 
> When this review is closed, I will update the emerge wiki
> 
> 
> Diffs
> -----
> 
> /trunk/kdesupport/emerge/bin/emerge.py 1220611 
> 
> Diff: http://svn.reviewboard.kde.org/r/6483/diff
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> Wolfgang
> 
> 


[Attachment #5 (text/html)]

<html>
 <body>
  <div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
   <table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 \
solid;">  <tr>
     <td>
      This is an automatically generated e-mail. To reply, visit:
      <a href="http://svn.reviewboard.kde.org/r/6483/">http://svn.reviewboard.kde.org/r/6483/</a>
  </td>
    </tr>
   </table>
   <br />





<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: \
10px;">  <p style="margin-top: 0;">On February 14th, 2011, 3:24 p.m., <b>Wolfgang \
Rohdewald</b> wrote:</p>  <blockquote style="margin-left: 1em; border-left: 2px solid \
#d0d0d0; padding-left: 10px;">  <pre style="white-space: pre-wrap; white-space: \
-moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: \
break-word;">now I actually found a note in the wiki about a short path option in \
kdesettings.

but I lost too much time with this - I do want to make sure this does never happen \
again.</pre>  </blockquote>







</blockquote>

<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: \
-pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">emerge provides two \
strategies in thia area: 

1. path substition by drive letters, which has to be configured in kdesettings.bat \
(you already refered to this)  2. short path usage - replace pathes by the short \
form. This feature is currently package based and could be activated by setting \
self.subinfo.options.useShortPathes -  see EmergeBase.__adjustPath() and where is is \
used for more details.  both strategies could be used together 

There are several limits in this area - nmake, mingw32-make, cmake, command line, \
each one has its own different limit

I found some related thread: 

http://lists.kde.org/?l=kde-windows&amp;m=125717156605667&amp;w=2
http://www.cmake.org/pipermail/cmake/2008-August/023279.html
http://lists.kde.org/?l=kde-windows&amp;m=124222975100566&amp;w=2

> From my personal experience does mingw builds have more problems as msvc builds and \
> the most annoying package is qt 

Ralf 

</pre>
<br />








<p>- Ralf</p>


<br />
<p>On February 14th, 2011, 3:18 p.m., Wolfgang Rohdewald wrote:</p>






<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" \
style="background-image: \
url('http://svn.reviewboard.kde.orgrb/images/review_request_box_top_bg.png'); \
background-position: left top; background-repeat: repeat-x; border: 1px black \
solid;">  <tr>
  <td>

<div>Review request for kde-windows.</div>
<div>By Wolfgang Rohdewald.</div>


<p style="color: grey;"><i>Updated Feb. 14, 2011, 3:18 p.m.</i></p>




<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: \
1px solid #b8b5a0">  <tr>
  <td>
   <pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: \
-moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: \
break-word;">On windows, gcc/g++ only take a maximum of 8192 chars for command line \
arguments. If they get more they will not complain but strange things will happen \
like compiler segfaulting or gcc misinterpreting the arguments at around position \
8192. I did not report this as a gcc bug, maybe somebody else already is registered \
wherever that can be done. I was using mingw4.

So emerge.py now first checks - it allows a maximum of 10 chars like in c:\kderoot. \
This results in command line lengths up to around 7700 (maybe more, this is what I \
saw).

I was using kderootsvn which makes gcc die when compiling \
c:\kderootsvn\download\svn-src\qt\src\3rdparty\sqlite\sqlite3.c, the command line \
having a length of 8214

When this review is closed, I will update the emerge wiki</pre>
  </td>
 </tr>
</table>





<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">

 <li>/trunk/kdesupport/emerge/bin/emerge.py <span style="color: \
grey">(1220611)</span></li>

</ul>

<p><a href="http://svn.reviewboard.kde.org/r/6483/diff/" style="margin-left: \
3em;">View Diff</a></p>




  </td>
 </tr>
</table>








  </div>
 </body>
</html>



_______________________________________________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows


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

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