Re: [Bacula-devel] Cygwin

[Robert N. <ro...@th...>]

I currently build the Windows port in 3 environments.
	Windows Visual Studio 2005 (I open the bacula.sln file :-)
	MinGW w/ Msys on Windows (I copy the win32/Makefile.inc.native to
Makefile.inc)
	MinGW using Linux Cross Compiler (I copy the
win32/Makefile.inc.cross to Makefile.inc)

I do the primary development using Visual Studio (much better diagnostics,
debugging tools, etc).  I can connect to remote machines and debug running
services using the IDE.

I do the initial port to MinGW w/ Msys on Windows.  Once again better tools,
much faster than X-Windows to my Linux machines.

I do the final testing using the Linux Cross Compiler.

Gdb sucks! :-)  But it does work for those MinGW specific cases and for
analysing crashes.

You can use the MinGW on Windows using either Msys or Cygwin.  There is no
difference in the code.  The only time you need Cygwin specific #ifdefs is
if you want to use the Cygwin unix emulation.  So if there are no objections
I'll remove the Cygwin #ifdefs as part of my cleanup.  Cygwin users can
still run the MinGW development environment on top of Cygwin.


-----Original Message-----
From: Kern Sibbald [mailto:ke...@si...] 
Sent: Monday, June 12, 2006 11:43 PM
To: Robert Nelson
Cc: bacula-devel 
Subject: Re: Cygwin

On Tuesday 13 June 2006 03:13, Robert Nelson wrote:
> Now that we have the mingw32 build are we still going to support cygwin?

The original cygwin code is no longer supported, since the compiles have
been 
done with the Microsoft compiler for some time.  Generally, I remove old
code 
one or two releases after the code is no longer used, but since I dislike 
working on Windows code so much, I have never done the cleanup for cygwin.

That said, I could see doing the cross-compiling in a cygwin environment as 
well as the current way of doing it on Linux. It is probably not something I

am going to actively work on, but I could imagine that some Windows user 
might prefer such a way of building Bacula rather than building it on a
Linux 
system.  This doesn't mean that we need to keep the HAVE_CYGWIN tags though.

>
> I've been going through the code trying to clean up the WIN32 ifdef's and
> implementing missing functionality.

That is a good thing.  Please try to keep all #ifdeffing to an absolute 
minimum.  In the next release after 1.40, I am going to remove virtually all

#ifdefs from the core code -- over time with lots of little submissions, it 
has become a bit of a mess -- see src/file/acl.c as an example; also the
zlib 
code in backup.c and restore.c (if I remember well).  I think we can remove 
99% of all #ifdefs.

-- 
Best regards,

Kern

  (">
  /\
  V_V