Message-ID: <002f01c214f6$a4c799d0$0100a8c0@p4> From: "Andrew Cottrell" To: References: <3D08B922 DOT E328F8B8 AT phekda DOT freeserve DOT co DOT uk> <2950-Sat15Jun2002191538+0300-eliz AT is DOT elta DOT co DOT il> <20020615224122 DOT GA26949 AT kendall DOT sfbr DOT org> Subject: Re: DJGPP 2.04 Date: Sun, 16 Jun 2002 15:24:42 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Reply-To: djgpp-workers AT delorie DOT com > -: Making the *.zip files and uploading them to DJ's server, tracking > > Can nightly or weekly builds of cvs djdevNNN be done on DJ's server (each > new build replacing the previous one)? These builds shouldn't appear on > SimTel, of course, but easy availability of "pre-alpha" djdevNNN could > make it much easier (e.g., for those who can't build all that stuff at > home) to continuously test the WIP. I suggest that a more practicle way could be to do weekly builds of the cvs djdevNNN and bi-weekly or monthly builds of the other packages. Who would use nightly builds as it would take someone more than a day to use the build? I have also found that using LIBC by itself with your own application may only test a very small proporation of the LIBC code, but if you are using updated GCC/BNU etc which have been built with teh LIBC code then allot more LIBC code will be tested without allot of effort. What I have been doing with the CVS 2.04 builds at clio is as follows, there are some shortcuts due to time constraints and there are some items duplicated because it ensures that what I upload is at least able to be re-built with the binaries that are uploaded. The process is:- a) Get a CVS update b) Check for merge problems in the update & fix if possible by 1) update to the latest file or 2) if I am fixing a bug and I need to test then manually merge the two changes (and yes this has occured allot becuase I may be working on one bug while Charles is working on a different bug for XP and the same file is affected) c) Check for updated packages & download them & install d) Build the updated packages from c) manually using the instructions in the package. Install the re-built package. e) Update my build all batch file to include the updated / new package from c) above f) Start the build. g) Wait for the build to finish (this also installs the exes) h) Check the dates of the files in the bin directory to ensure that all the packages built. If there is a problem then resove the problem. i) Check the dates on the libs in the lib directory to ensure that all the relevant libs were re-built. I also have some contrib type libs which I do not rebuild. If there is a problem then resolve it. j) Once all the exes and libs are okay one then proceeed. k) If there are significant changes in the LIBC update do a complete re-build od LIBC & packages to verify that there are no nasties lurking in the newly created exes l) Check the bin and lib directory again m) Produce the zip files n) Update the 2.04 HTML page at clio o) Upload the files p) Delete the redundant zip files (old packages which were replaced from step c) above). Overall this does not take allot of actual time, say 3-8 hours over 2-3 days. Actual PC time used is about 24 hours due to me being on a 56K dial up modem so the upload time is huge. I try to do a get of the CVS libc code at least once a week and do steps a) through i). This takes a few hours of work. The full process gets done on an ad-hoc basis after major W2K or XP or other bugs are fixed, or allot of minor bugs are fixed, or after a GCC update has occured. In the last 3-4 months I have averaged one upload a month, but at the moment I am in the process of another release just two weeks after the last one because of the GCC 3.1 changes required in the LIBC code. Regards, Andrew