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

List:       kde-commits
Subject:    www/areas/quality/develop/cvsguide
From:       Carlos Leonhard Woelz <carloswoelz () imap-mail ! com>
Date:       2005-05-26 21:55:48
Message-ID: 1117144548.199170.19271.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 418547 by cwoelz:

Forgot to add that kdesvn-build has a different log location...

 M  +11 -1     buildstep.php  


--- trunk/www/areas/quality/develop/cvsguide/buildstep.php #418546:418547
@@ -779,9 +779,16 @@
 
 <p>Before building any of the modules, kdesvn-build will normally perform a "svn \
update" or "svn checkout" of all of the listed modules. "svn update" synchronize your \
local copy of a module with the latest copy in the CVS repository on the server. \
Since you just did a checkout of all the modules, you don't need to do this.  The \
"--no-svn" causes kdesvn-build not to do the "cvs update".</p>  
-<p>When kdesvn-build completes, examine the log files to see if any of the modules \
did not build and install successfully. The problematic log files are listed in the \
end of the script output. Fix the problems and rebuild. For example to tell \
kdesvn-build to build (and install) the kdeaddons module:</p> +<p>When kdesvn-build \
completes, examine the log files to see if any of the modules did not build and \
install successfully. The problematic log files <strong>are listed in the end of the \
script output</strong>. kdesvn-build places the log files inside the "log" folder, \
which contains folders named after the date of the execution of the script (you can \
always get the latest log using the "latest" symlink). There, you will find folders \
named after the modules you are building. Inside them, there are separate log files \
for svn, configure, build system, build and install output.</p>  
 <pre style="border: 1pt dashed #D1D1D1; margin-left: 2em; padding: 1em;">
+#Viewing the configure log for the latest build of kdelibs:
+less /home/kdedev/src/kde/log/latest/kdelibs/configure.log
+</pre>
+
+<p>Fix the problems and rebuild. For example to tell kdesvn-build to build (and \
install) the kdeaddons module:</p> +
+<pre style="border: 1pt dashed #D1D1D1; margin-left: 2em; padding: 1em;">
 cd /home/kdedev/src/kde
 ./kdesvn-build --no-svn kdeaddons
 </pre>
@@ -851,6 +858,9 @@
 
 <pre style="border: 1pt dashed #D1D1D1; margin-left: 2em; padding: 1em;">
 less /home/kdedev/src/kde/log/kdelibs*
+# Or, if you are using the automatic build process, check the output of
+# kdesvn-build to find the log file that shows the error.
+# less /home/kdedev/src/kde/log/latest/module/log-name.log
 </pre>
 
 <p>Look through the log file to find the cause of the error.  It is normal to see \
warning messages.  You are looking for errors.  Finding errors in the log files or in \
the terminal output, and knowing what to do about them is a bit of an art. As you \
gain experience, it will get easier.  Try looking at the configure output first, then \
the last lines displayed. Here's some handy keyboard commands to use in less ("man \
less" for more info).</p>


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