|
Boost : |
From: Braden N. McDaniel (braden_at_[hidden])
Date: 2000-02-23 23:19:01
On Wed, 23 Feb 2000, Beman Dawes wrote:
> That sounds to me like it could coexist with other install tools as
> long as the directories were separate.
It probably can. I'm involved in another project where we use the GNU
tools for the Unices, and then we have persons responsible for maintaining
project files for popular IDEs on Windows and the Mac. We haven't really
addressed the issue of actual installation on those platforms, though.
> 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
binaries.)
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.
-- Braden N. McDaniel braden_at_[hidden] <URL:http://www.endoframe.com>
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk