On Saturday 04 March 2006 01:50, Scott Barninger wrote: > On Fri, 2006-03-03 at 19:33 -0500, Dan Langille wrote: > > AFAIK, cygwin is no longer used. Everything is native Windows now. > > > > "If you want to build the Win32 binaries, you will need a Microsoft > > Visual C++ compiler (or Visual Studio)." > > > > Does that help? > > I am getting ready to start building the win32 client for releases > again, just waiting for VC++ to arrive. Looking at > http://www.bacula.org/developers/Bacula_Porting_Notes.html I see: > > If you want to build the Win32 binaries, you will need the full Cygwin > 1.5.5 release. Although all components build (console has some > warnings), only the File daemon has been tested. Please note that if you > attempt to build Bacula on any other version of Cygwin, particularly > previous versions, you will be on your own. >
I think that is somewhat outdated. I fixed it a couple of days ago (I think). The current Cygwin version is something like 1.18 and more importantly, except for the build process scripting, Bacula no longer uses Cygwin (in the binaries), and thus Bacula is very largely independent of the Cygwin version -- that is it should build fine on any version. By the way, if you have not yet received your VC++, there is a problem. I'll see if I can track it down this afternoon ... Best regards, Kern ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
