From: Kern S. <ke...@si...> - 2006-07-28 07:20:53
|
On Friday 28 July 2006 02:25, Dan Langille wrote: > On 27 Jul 2006 at 17:22, Robert Nelson wrote: > > > 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. > > What might be useful would be a beta release of the Windows client... > and allows people that do/can not build to help in the testing. Yes, we are working on getting a beta release out. There are still a few more steps to do first. 1. Run build/regression of core code on FreeBSD and Solaris, 2. Put 1.39.x into production here for 2 or three days. 3. Document it at least in the ReleaseNotes. 4. make the beta release. > > -- > Dan Langille : Software Developer looking for work > my resume: http://www.freebsddiary.org/dan_langille.php > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys -- and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel > |