The downside to the nmake-based make files in the 4.0 build is the header file dependency management is a completely manual process....and the initial setup didn't take into account any include file nesting, but rather just picked up what the modules happened to be directly including at the time.  The autoconf process generates the dependency lists automatically, which gives us a cleaner, more reliable build.  If there are some native windows tools available that can allow that step to be automated, then I'm guess I'd be ok with that too. 


On Jan 30, 2008 8:49 AM, Mark Miesfeld <> wrote:
On Jan 30, 2008 4:39 AM, Rick McGuire <> wrote:

> Mark,
> Is it possible that what David is doing will work with either the cygwin
> tool set or the GnuWin32 versions?  I'm not particularly tied to using
> cygwin....I just want a unified build process and make files.

It is possible, I'm not sure.  I don't think the autoconf stuff with
the GnuWin32 versions works.  Actually it may not even be there.  If
it was only a matter of having a make file that used tools like rm,
mkdir, and cat, etc., it would work with GnuWin32.  I don't think the
autoconf stuff will work, have to see.

Don't get me wrong, I am much in favor of getting ride of the current
.bat file driven Windows build.  But, I liked the nmake Windows build
on the 4.0 stuff.

I understand that it would be nice to have only one thing to update
when a new file was added or deleted.  Maybe you could just update the
unix side and assign updating the Windows nmake side to me.  Sort of
like how you assign a bug to Lee for inclusion in the change log.
<grin> Just kidding of course.

Mark Miesfeld

This email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
Oorexx-devel mailing list