Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <060301c1a2af$fef52620$93c0b0d0@v505>
From: "William A. Rowe, Jr." <wrowe@covalent.net>
To: <dev@apr.apache.org>,
	"Christian Gross" <christiangross@yahoo.de>
References: <5.1.0.14.2.20020121183841.031501a0@mail.devspace.com>
Subject: Re: WIN32 Builds and complexity
Date: Mon, 21 Jan 2002 13:15:28 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

From: "Christian Gross" <christiangross@yahoo.de>
Sent: Monday, January 21, 2002 11:45 AM


> I do not want to seem like a whiner, but I would like to say that the WIN32 
> Apache build test process has become utterly complex.  Here are the 
> following reasons:
> 
> 1) AWK is necessary and my AWK from Cygwin crashes everytime it is 
> used.  My Cygwin installation is up to date with the latest edition.

Sorry, then patch cyg-awk, or use another (see win_compling.html).  I never
expect Cyg tools to run except within the Cyg shell.


> 2) Everything within the VC++ application is stored within in their 
> respective DEBUG directories.  With so many pieces now debugging has become 
> very difficult.  You cannot simply move the DLL since then the debugger 
> becomes confused.

No, if you make makefile.win, or launch the InstallBin target, they work.


> 3) To set breakpoints the DLL's have to pre-loaded into the debug space, 
> otherwise you get a constant error of breakpoint not being able to set.

You can't do this without distributing the .opt file that corresponds to the
.dsw file.  You can't do this, since .opt is localized to your machine paths.


> My suggestion is to create a project for building versions of Apache that 
> people can use to build production capable releases.  But for the debug 
> crowd there is a simple project that is like the previous Apache build, 
> where you loaded one project, hit build, set a breakpoint and debugged your 
> sources.
> 
> I can do this if so desired.

This is why I do _exactly_ that with the 'InstallBin.dps' makefile.mak project.
You are then debugging binaries deposited into your 'installed server'.  We
can look at exactly what can be toggled, but this should be trivial.

I wish the .opt debugging info were global, unfortunately, it is not.

Bill