Date: 2000-02-24 05:29:36
>The standard operating procedure for users of GNU-style tarballs is:
> 1. Unarchive the tarball and change to the directory.
> 2. ./configure
> 3. make
> 4. make install
>> Let me try it for Win32 platforms. If that works OK, I will put a
>> .zip file in the vault, and people can then try to add directories
>> with scripts for other platforms.
>Just in case I wasn't clear before, automake needs to invade the source
>tree. The primary consequence of that the build system's Makefile.in's
>end up in the source tree, as do the Makefiles. (Though the latter aren't
>generated until configure time, when the user is preparing to build the
>I'll wait until I have your zip file and a clear picture of the directory
>structure therein to comment further. I don't know of any particular
>strucure that would pose a problem for automake (it's pretty flexible),
>the only issue is that it needs to invade it.
Why not insist for Windows on a Cygwin installation? Then we'll have an
environment, that supports the procedure described above in the same way for
Windows as for Unix. I've built meanwhile enough Unix tools successfully for
Windows that were prepared for Cygwin. This would minimize the maintenance
effort and the boost may just provide a link to Cygwin to get an installation of
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk