My hope/goal is to keep the build & install process as simple as
reasonably possible.
It's been rumoured that Rob Browning said:
> ... keep forked version of g-wrap indefinitely, ...
The goal of all of the packages on the lib directory is that they are
for the short term, to simplify compile
Matt Armstrong <[EMAIL PROTECTED]> writes:
> Makefile.in is a generated file in an automake system -- it is
> generated from Makefile.am files. We could add your make rules to a
> Makefile.am, but it gets to be a pain because the rules must somehow
> be hooked into the existing automake rules (f
On Thu, Jul 15, 1999 at 12:07:35AM -0500, Rob Browning wrote:
> Matt Armstrong <[EMAIL PROTECTED]> writes:
>
> > So, I think I'll start over and proceed along these lines. Lemme
> > know if either (a) you are an automake guru and would like to take
> > over where I left off or (b) you have any o
Matt Armstrong <[EMAIL PROTECTED]> writes:
> So, I think I'll start over and proceed along these lines. Lemme
> know if either (a) you are an automake guru and would like to take
> over where I left off or (b) you have any other thoughts.
Well, perhaps we should talk about this. How substantia
I've gotten pretty far into the automake conversion. The last
bit remains and, unfortunately, is proving to be a real pain in
the butt. The last straw for me was the g-wrap stuff. We
./configure, make and install g-wrap as part of the gnc compile
process. There is no straightforward way to do
