Content-Type: multipart/alternative; boundary="----=_NextPart_001_02DE_01C6B1A1.2EC43760" ------=_NextPart_001_02DE_01C6B1A1.2EC43760 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To make life easier I suggest the following steps when doing a cvs update to pickup all the win32 changes. cd src/win32 make clean cd ../../.. make clean cvs -q update If you are just building the Microsoft Windows version there is no longer any need to run configure. You can build both versions in the same tree. The Unix build doesn't touch anything below the win32 directory and the Microsoft Windows build doesn't touch anything above it or rely on any configure'd files. ------=_NextPart_001_02DE_01C6B1A1.2EC43760 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
To make life = easier I=20 suggest the following steps when doing a cvs update to pickup all the = win32=20 changes.
 
    cd=20 src/win32
    make=20 clean
    cd=20 ../../..
    make=20 clean
    cvs -q=20 update
 
If you are just = building=20 the Microsoft Windows version there is no longer any need to run=20 configure.
 
You can build = both versions=20 in the same tree.  The Unix build doesn't touch anything below = the=20 win32 directory and the Microsoft Windows build doesn't touch anything = above it=20 or rely on any configure'd files.
 
= ------=_NextPart_001_02DE_01C6B1A1.2EC43760--