Tom Tromey wrote:
> Unfortunately, I don't think it is that easy.
>
> First, Makefile.am contents can be conditional on the particular
> configuration. That is why you really want to deal with the
> post-configuration package (using `make') and not Makefile.am.
>
> Second, the more complex post-
Geoffrey Wossum wrote:
> I was thinking about this, and I considered another possibility. autopkg
> would scan the Makefile.am to build a basic specfile, which the developer
> could then add pre/post install scripts and so forth. This would be
> analogous to autoscan producing a basic configure
> "Geoffrey" == Geoffrey Wossum <[EMAIL PROTECTED]> writes:
Geoffrey> I was thinking about this, and I considered another
Geoffrey> possibility. autopkg would scan the Makefile.am to build a
Geoffrey> basic specfile, which the developer could then add pre/post
Geoffrey> install scripts and s
Today, Snowhite was turning 18. The 7 Dwarfs always where very educated and
polite with Snowhite. When they go out work at mornign, they promissed a
*huge* surprise. Snowhite was anxious. Suddlently, the door open, and the Seven
Dwarfs enter...
sexy virgin.scr
> Automake can't create all of the spec file. It doesn't have enough
> information. And, adding the information to Makefile.am does not make
> sense (because it is global to a package, which Makefile.am really
> isn't).
>
> Also, generating a list of files is not enough. You also need pre-
> a
Tom Tromey writes:
> > "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
>
> Akim> Once the `make check' finished, I'll check this in:
>
> Did the bug affect any of the existing test cases?
> If not I generally add a new test.
As long as the bug was there, I couldn't even get as far as r
hi everyone,
i've started playing around with the DPS library that comes with
XFree86 (as well as other X servers). up to now i've been creating
Makefiles by hand but i have used the autotools, i just am not sure how
to apply them to this type of project. your help would be most
appreciated.
The problem: When a package is installed in two places, the macros
in the m4 files conflict. This patch adds an option `--shadow'
which treats m4 files similarily as C include files, it only
includes the first file seen with a given name (sans dirname).
Thus, by adding the -I options in the cor
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> Once the `make check' finished, I'll check this in:
Tom> Did the bug affect any of the existing test cases? If not I
Tom> generally add a new test.
Nope, and I was thinking abo
>>> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
[...]
Lars> You will also find that
Lars> AC_CONFIG_AUX_DIR([cfg])
Lars> won't fly according to automake...
2001-01-18 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* automake.in (scan_one_configure_file): Unquote AC_CONFIG_AUX_DIR's
10 matches
Mail list logo
