Nut upsdev - May 2011 - Merging windows_port branch

Hello,

As you may have noticed, a first running version of nut for
Windows has been released some time ago. In order to validate the
possibility to merge the windows_port branch to the trunk, I have
produced a patch file using the "svn diff" command.
This patch couldn't be applied directly and the use of a merging tool is
still needed. It is only intended to be reviewed so that we have a
consensus on the merging of those two branches.

Since it's too big for the mailing list, you can download it here :

http://www.networkupstools.org/tmp/

The file is called patchfile.zip.
The other file (log.zip) contains logs of the "configure" and
"make"
commands on my Windows build machine for reference.

Please feel free to send any comments.

Regards,
Fred

-- 
Team Open Source Eaton - http://powerquality.eaton.com

--------------------------------------------------------------------------

Please be sure to merge r2990 and any other recent changes (r2993,  
r2994?) onto windows_port as well. (The patch file dated "24-May-2011  
16:10" seems to revert those changes.) A good way to catch things like  
this is to indicate the range of revisions which you are merging in  
the commit message, and check the last merged revision against the  
trunk. (Newer versions of Subversion supposedly automate this process,  
but I am skeptical.)

Also, please ensure that the C files have Unix-style line endings when  
they get checked in. Setting the svn:eol-style property to "native" on
those files will cause LF to be translated to CR+LF on Windows  
platforms.

I'll start a build of the windows_port branch on a *nix machine  
shortly, but have you been able to do any regression testing of that  
branch with a non-Windows machine?

Something looks strange here:

http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/12/steps/configure/logs/stdio

checking for socklen_t... yes
./configure: line 6965: test: =: unary operator expected

-- 
- Charles Lepple