ool is an overkill. AC_PROG_RANLIB should be
> enough. (Note: I have pratically no real experience in using libtool
> and in building static libraries with automake, so correct me if I'm
> wrong!).
Is there any reason to avoid LT_INIT and use AC_PROG_RANLIB
instead? I thought that AC_PROG_RANLIB was considered
deprecated, so that LT_INIT would be preferred here.
--
William Pursell
([
src/app/Makefile
src/Random/Makefile
Makefile
])
AC_OUTPUT
Also, instead of running aclocal, libtoolize, autoconf, and automake
by hand, just run autoreconf -i
--
William Pursell
it! I bet the engineer's windows don't have curtains.
Probably no curtains, but they do have windshield wiper to clear away the cruft.
--
William Pursell
bad idea. The project maintainer should not be
deciding where the user must install the library. If
the user wants to install ezproject in /opt/ezproject, he
should to be able to do 'configure --libdir=/opt/ezproject/lib',
but your setup will not allow that.
--
William Pursell
privileged".
Do you mean only those people who have access to clone the git
repository?
--
William Pursell
lem; if you have the ability
to compile and install your own code on the box, then you
can install automake as well. (Where 'install' might mean
'put in $HOME')
--
William Pursell
file.am
can contain:
@MY_DEFAULT_RULES@
This mostly works, but there are a few cases where I need to
have the generated snippet file be just the rule, so I can do
things like:
check-local:
@MY_LOCAL_RULES@
The question is: is that a reliable technique, or is it a
ridiculous hack that will someday come to haunt me?
--
William Pursell
Ralf Wildenhues wrote:
> Hi William,
>
> * William Pursell wrote on Fri, Jan 30, 2009 at 08:02:58AM CET:
>> I've written a simple patch that lists the tests that
>> misbehaved (failed or unexpectedly passed), one
>> per line, in the banner.
>
>> Do you
lity a run time
environment option, an automake option (like color-tests),
or just leave it in for all invocations of make check?
(or do you think it's a bad idea?)
--
William Pursell
e variables to a
stamp file or something along those lines. That
seems a very fragile solution...or is there
already a different solution?
--
William Pursell
Jan Engelhardt wrote:
> On Monday 2008-12-15 08:32, William Pursell wrote:
>> Jan Engelhardt wrote:
>>
>>> third round here of the automake-tranquility patch from me.
>>> Updates from previous attempts:
>> I've been looking through the archive and haven
is incorporated.
Jan, which commit was your patch made against?
I've been trying to patch 3e155 (*NEWS:Fixtypo),
but the line numbers are off a bit. I'm having
some issues applying your patch and would really
like to try it out. It would help me if I knew
where it came from.
--
William Pursell
tory from the source
directory.
--
William Pursell
Ralf Wildenhues wrote:
Hello William,
* William Pursell wrote on Thu, Oct 09, 2008 at 06:28:18PM CEST:
bash-3.2$ make
CDPATH="${ZSH_VERSION+.}:" && cd ../automake &&
perllibdir="/Users/williampursell/git/build-automake/lib:./lib"
"/Users/williampu
Here's a patch to prevent that grammatically
incorrect text: "All 1 tests passed"
Unfortunately, I haven't been able to build
automake, so I cut-and-pasted from here into
a Makefile to check the syntax. It's a pretty
simple patch, and hopefully I haven't flubbed
OOK', '', 'FILENAME_FILTER', ...) called at
/Users/williampursell/git/build-automake/automake line 3688
Automake::handle_dist() called at
/Users/williampursell/git/build-automake/automake line 7493
Automake::generate_makefile('Makefile.am', 'Makefile.in')
called at /Users/williampursell/git/build-automake/automake line 7834
make: *** [../automake/Makefile.in] Error 1
--
William Pursell
and
have leveled debugs in the code.
--
William Pursell
Ralf Wildenhues wrote:
* NightStrike wrote on Sun, Jan 13, 2008 at 10:08:58AM CET:
AC_INIT takes in parameters the name of the package, its version
number, and a contact address for bugreports about the package (this
address is output at the end of ./configure --help, for instance).
That's not
Andreas Schwab wrote:
William Pursell <[EMAIL PROTECTED]> writes:
I'd like to get away from AC_SUBST_FILE, but I don't see a way
around the manner in which automake is building the Makefile.
Is there a way to construct a generic target via AC_SUBST?
How about using AM_CON
I've been using AC_SUBST_FILE to put common targets into my
makefile.am's. eg, Makefile.am contains:
@FOO_TARGET@
where configure.ac contains
FOO_TARGET=foo_target
AC_SUBST_FILE(FOO_TARGET)
and foo_target contains:
foo:
echo foo
I would like to do this via AC_SUBST, but this complet
20 matches
Mail list logo
