|
From: <sv...@va...> - 2005-06-30 00:28:01
|
Author: njn Date: 2005-06-30 01:27:57 +0100 (Thu, 30 Jun 2005) New Revision: 122 Log: Update info about 2.4 vs. 3.0 repos. Modified: trunk/devel/cvs_svn.html Modified: trunk/devel/cvs_svn.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/devel/cvs_svn.html 2005-06-11 23:53:03 UTC (rev 121) +++ trunk/devel/cvs_svn.html 2005-06-30 00:27:57 UTC (rev 122) @@ -10,18 +10,53 @@ <a href=3D"http://subversion.tigris.org/">Subversion</a> (SVN) at valgrind.org.<br /> =20 -The development valgrind-3.0 line is now in SVN at valgrind.org.<br /> +The actively developed valgrind-3.0 line is now in SVN at valgrind.org.<= br /> =20 -The stable valgrind-2.4 line continues to be kde.org, now also in SVN, a= t +The old valgrind-2.4 line continues to be kde.org, now also in SVN, at least for the moment.</p> =20 -<p>If you are doing any development work other than bug fixes for 2.4, p= lease -do them on the 3.0 line against the valgrind.org repository!</p> +<p>If you are doing any development work, please do it on the 3.0 line +against the valgrind.org repository!</p> =20 =20 <div class=3D"hr_brown"><hr/></div> -<h2>The stable valgrind-2.4 line</h2> +<h2>The Valgrind-3.0 development line</h2> =20 +<p>If you want to browse the 3.0 repository, you can use the web +based interface:=20 +<a href=3D"http://svn.valgrind.org/">http://svn.valgrind.org/</a>.</p> + +<p>To check out code on the 3.0 line (anonymous, read-only SVN=20 +access), proceed as follows. Note that=20 +the 3.0 line has been split into two pieces: Vex, a library that +provides dynamic translation services, and Valgrind proper. You=20 +need both pieces. Do this:<br /> +<code> svn co svn://svn.valgrind.org/vex/trunk vex</code><br= /> +<code> svn co svn://svn.valgrind.org/valgrind/trunk valgrind= </code><br /> +<code> cd vex && make clean version all</code><br /> +<code> cd ../valgrind</code><br /> +<code> ./autogen.sh</code><br /> +<code> ./configure --prefix=3D... --with-vex=3D/path/to/vex<= /code><br /> +<code> make install</code><br /> +</p> + +<p><b>Note:</b> as of late June 2005, the 3.0 line has seen great +upheaval. Nonetheless, it builds and works well on x86/Linux <b>and +AMD64/Linux</b> and is eminently usable. It also has some functional +improvements over the current 2.4.0 release, mostly in Memcheck's handli= ng +of SSE/SSE2 code. +</p> + +<p>On PPC32/Linux it is just coming to life, but cannot run anything mor= e +than tiny programs. We expect this will improve rapidly. For the time +being, however, don't bother to try building on PPC32/Linux unless you a= re a +die-hard developer and are prepared for serious breakage. +</p> + + +<div class=3D"hr_brown"><hr/></div> +<h2>The old Valgrind-2.4 line</h2> + <p>If you want to browse the 2.4 repository you can use the=20 <a href=3D"http://websvn.kde.org/trunk/valgrind/">web based interface</a= >.</p> =20 @@ -42,36 +77,4 @@ =20 =20 =20 -<div class=3D"hr_brown"><hr/></div> -<h2>The unstable valgrind-3.0 development line</h2> =20 -<p>If you want to browse the 3.0 repository, you can use the web -based interface:=20 -<a href=3D"http://svn.valgrind.org/">http://svn.valgrind.org/</a>.</p> - -<p>To check out code on the 3.0 line (anonymous, read-only SVN=20 -access), proceed as follows. Note that=20 -the 3.0 line has been split into two pieces: Vex, a library that -provides dynamic translation services, and Valgrind proper. You=20 -need both pieces. Do this:<br /> -<code> svn co svn://svn.valgrind.org/vex/trunk vex</code><br= /> -<code> svn co svn://svn.valgrind.org/valgrind/trunk valgrind= </code><br /> -<code> cd vex && make clean version all</code><br /> -<code> cd ../valgrind</code><br /> -<code> ./autogen.sh</code><br /> -<code> ./configure --prefix=3D... --with-vex=3D/path/to/vex<= /code><br /> -<code> make install</code><br /> -</p> - -<p><b>Note:</b> as of late March 2005, the 3.0 line has seen massive -upheaval. It builds and works pretty well on x86-linux and is -eminently usable. In some ways is already better than the current -stable 2.4.0 release, mostly in its handling of SSE/SSE2 code. -</p> - -<p>On amd64-linux it is just coming to life, but is majorly broken in -various ways, and is not usable for anything useful yet. We expect -this will improve rapidly. For the time being, however, don't bother -to try building on amd64-linux unless you are a die-hard developer and -are prepared for serious breakage. -</p> |