On 1/4/24 06:00, Eric Gallager wrote:
So, `aclocal` has a flag to control this behavior: specifically, its
`--install` flag. Right now I don't see `aclocal` mentioned in the GNU
Coding Standards at all. Should they be updated to include a
recommendation as to whether it's better to put `--insta
On 2/3/23 16:07, ljh via Discussion list for automake wrote:
Hi,
It seems I can not use `--disable-assert` on Debian 11.
You need to call macro AC_HEADER_ASSERT in your 'configure.ac'
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/autoconf.html#Particular-Headers
Hi Karl,
On 20/1/22 09:05, Karl Berry wrote:
But if both are set, should the --aclocal-path argument replace
$ACLOCAL_PATH, or augment it (earlier of course)? I'm not sure.
FWIW, in autoconf the commandline -W takes precedence over environment
variable WARNINGS
https://www.gnu.org/savannah-
On 21/11/21 16:32, Billa Surendra wrote:
Then how-to install automake in target image.
Download the tarball from https://ftp.gnu.org/gnu/automake/
unpack and follow the instructions in INSTALL; typically somethings like
./configure
make
sudo make install
Peter
On 11/8/21 9:55 pm, Werner LEMBERG wrote:
Folks,
My current rule (in the top-level `Makefile.am`) is
nobase_dist_doc_DATA = doc/bar.html \
doc/img/baz.png
I think you wanna get rid of the 'nobase_' prefix (but haven't
tested).
If I do that, all files are ins
On 11/8/21 9:55 pm, Werner LEMBERG wrote:
Folks,
My current rule (in the top-level `Makefile.am`) is
nobase_dist_doc_DATA = doc/bar.html \
doc/img/baz.png
I think you wanna get rid of the 'nobase_' prefix (but haven't
tested).
If I do that, all files are ins
Hi Werner,
On 8/8/21 5:49 am, Werner LEMBERG wrote:
Folks,
My current rule (in the top-level `Makefile.am`) is
nobase_dist_doc_DATA = doc/bar.html \
doc/img/baz.png
I think you wanna get rid of the 'nobase_' prefix (but haven't tested).
Cheers,
Peter
On 24/6/21 3:02 am, Werner LEMBERG wrote:
As far as I know there is no way to disable this behaviour, although
I agree the automagic file inclusion can be a bit funky.
Yeah, it would be nice to have a means to control that.
There is the dist hook, which can be used to remove files from the
Hi Laurence,
On 15/4/21 6:35 am, Bob Friesenhahn wrote:
Most problems seem to stem from packages providing the generated files
from Autoconf, Automake, and libtool so that end users don't need to
have the tools available.
It will be easier for people here to help if you provide a bit more
in
On 3/14/2019 3:24 AM, Nick Bowler wrote:
Hello Craig,
On 2019-03-13, Craig Sanders wrote:
Is it possible to set the permission bits used by the default install
target in a Makefile.am?
To help try and illustrate what I mean, I present a code snippet from one
of my Makefie.am files.
Begin
Hi Kip and Nick,
On 12/30/2018 12:03 PM, Kip Warner wrote:
Almost! The problem is with the last rule you defined because a rule to
generate test-stop.log would have already been generated by Automake
and this would override it. I tested in my own source tree and
confirmed that:
automake-1.1
Hi Karl,
On 9/13/2018 7:53 AM, Karl Berry wrote:
After make check runs, if there were any failures, I'm wishing for a way
to have automake to automatically show the relevant test-suite.log.
I might be missing something, but I get that behavior in my automatic
builds by calling 'make check VE
On 9/2/2017 1:27 PM, Quinn Grier wrote:
You can fix this by generating the complete macro definitions before
Automake runs and including them in Makefile.am.
Another way to do this is to use
macro `AX_AM_MACROS_STATIC' in Autoconf Macro Archive
https://www.gnu.org/software/autoconf-archive/a
Hi Patrick,
On 6/3/2017 5:26 PM, Patrick Alken wrote:
Hi Peter,
Yes make distcheck is in fact failing (even with your modification).
The error is:
/bin/install -c -m 644 file.info
/data/palken/package/package-1.0+/_inst/share/info
/bin/install: cannot stat ‘file.info’: No such file or direc
Hi Patrick,
On 5/21/2017 5:16 PM, Patrick Alken wrote:
Hello,
I have a .info file (not generated by texinfo) and would like it to be
installed under 'make install'. I tried adding it like this:
info_DATA = file.info
but this gives the following error:
doc/Makefile.am:7: error: 'infodir'
On 11/02/2016 08:06 PM, Raphaël Halimi wrote:
Hi Peter,
Thanks for your answer.
Just to make sure I understand:
CLEANFILES += data/.dirstamp
data/.dirstamp:
@$(MKDIR_P) data
@: > $@
This creates a directory "data", and then a file ".dirstamp" in this
directory by redirecting t
Hi Raphael,
I have the following in my Makefile.am
CLEANFILES += data/.dirstamp
data/.dirstamp:
@$(MKDIR_P) data
@: > $@
data/foo.txt: data/.dirstamp
Cheers,
Peter
On 10/28/2016 05:46 AM, Raphaël Halimi wrote:
Hi,
I have a problem with parallel build trees (a.k.a. VPATH Bu
Hi Jürgen,
On 03/18/2016 01:28 AM, Juergen Sauermann wrote:
Hi,
I have received a bug-report saying that 'make distclean' fails for
GNU APL.
The error message is this:
make[2]: Entering directory `/home/eedjsa/projects/juergen/apl-1.5/src'
Makefile:837: .deps/apl-Archive.Po: No such file o
Hi Kees-Jan,
On 12/30/2015 05:52 AM, Kees-Jan Dijkzeul wrote:
On Tue, Dec 29, 2015 at 8:46 PM, Bob Friesenhahn
wrote:
>Try adding 'make clean' to your build steps.
>
>The best thing to do is to build outside of the source tree and use a
>separate build directory for each configure incantation
On 09/28/2015 08:20 PM, Robert Parker wrote:
I need to meet the requirements of 2 sets of users, the ordinary user who
is only interested `./configure; make; make install` and the power users
who want to start with `autoreconf`.
So far google search on the topic has only increased my confusio
On 09/01/2015 08:14 AM, Andy Falanga (afalanga) wrote:
Where can I get these standards?
https://www.gnu.org/prep/standards/
Cheers,
Peter
On 06/24/2015 10:20 PM, Harlan Stenn wrote:
So I notice that in automake-1.15 the distcheck stuff is now begin built
in _build/sub/. I am generating some files for our test framework that
want to access stuff in srcdir.
I have these .in files using @srcdir@, but with the change from _build
to
On 05/15/2015 10:36 AM, Arthur Schwarz wrote:
And, if I guess correctly, the user can write
"make check TESTSUITEFLAGS=-jN"
I've never seen TESTSUITEFLAG before, so I don't know.
As a nit-noy, don't you mean "processor" and not "cpu"? And
On 05/15/2015 12:24 AM, Arthur Schwarz wrote:
And as a simple question, why are you using "make -j8"? Shouldn't this
be part of the automake generated test code?
The short answer is because I wanna use 8 cpus. There is no sensible way
Automake can know how many cpus I wanna use.
$ make check
On 05/14/2015 01:20 AM, Arthur Schwarz wrote:
My question is is this the only way to use VERBOSE? The Automake
Manual seems to say that VERBOSE is a variable, not a make argument.
And, as a variable, if the user (you) can change it's value then the
appropriate way to do it is either: env VERBOS
uite.log file.
I have tried to set VERBOSE in my Makefile.am to '1' and to 'yes' and "yes"
and just plain yes. The test-suite.log file does not output. Am I missing
something? How is VERBOSE supposed to be turned on?
Usually I run my tests with something like this:
make check -j8 VERBOSE=1
hth,
Peter
--
Peter Johansson
exit tatus
Shell variables are referred to with double dollar sign in a Makefile:
echo exit $$status
hth,
--
Peter Johansson
blems) so it's set
as .PHONY target.
I'd let it depend on 'configure' and then it's re-generated (at least)
every time you bump your VERSION, which should happen every time you
release.
Cheers,
Peter
--
Peter Johansson
e/autoconf-archive/ax_add_am_macro_static.html#ax_add_am_macro_static
Cheers,
--
Peter Johansson
Hi Andy,
On 03/10/2015 08:23 AM, Andy Falanga (afalanga) wrote:
I try taking out the *.cpp file and try again with the same error but with the *.h. If I
take out the *.h file, all is well again and "make dist" is happy and fine.
Why is it picky with files ending with *.cpp and *.h if these t
foo/bar.o'.
http://dev.thep.lu.se/svndigest/changeset/1581
Cheers,
Peter
--
Peter Johansson
On 01/29/2015 05:30 PM, Asaf Dalet wrote:
install-exec-hook:
chmod +s $(sbindir)/foo
Try
install-exec-hook:
chmod +s $(DESTDIR)$(sbindir)/foo
hth,
--
Peter Johansson
On 06/09/14 02:20, Jack Bates wrote:
How do I make another target a prerequisite of the dist target?
I want my "man" target to be a prerequisite of the dist target,
so when I run "$ make dist" it calls my "man" target.
EXTRA_DIST is not working directly, I suppose, but I would still try
that p
On 22/08/14 10:55, David Ventimiglia wrote:
Hi,
Does Automake provide any kind of extension mechanism so that one can
produce, and possibly share, useful Makefile fragments?
Hi David,
What I've chosen to do is to write autoconf macros that generate these
Automake fragments, so all I need t
ware/automake/manual/automake.html#Extending
Cheers,
--
Peter Johansson
On 18/05/14 10:54, Bob Friesenhahn wrote:
Is there a safe way to change DEFAULT_INCLUDES to only include what is
needed?
Hi Bob,
Have you looked at automake option 'nostdinc'?
Hope that solves it.
Peter
e very large.
Thanks,
— Pavan
--
Peter Johansson
downloaded from
somewhere? Many many thanks in advance,
- Gao
Sounds like you need to set the search path; have a look at `dirlist' in
the manual. If you provide more details on what error you experience,
it's easier for people to help.
Cheers,
--
Peter Johansson
So perhaps autoreconf needs a late test that if aclocal.m4 is newer than
config.h.in, we touch config.h.in .
This way, if nothing is updated then nothing gets touched. But if
aclocal.m4 gets updated we'll avoid this particular problem.
--
Peter Johansson
o I
don't see this problem. If you think that is too expensive, you could
set environment
variable AUTOHEADER with something like:
AUTOHEADER="autoheader -f" autoreconf -vi
Changing the behaviour of autoheader, I suspect will be met by some
significant resistance.
Cheers,
--
Peter Johansson
On 09/25/2013 08:00 AM, Werner LEMBERG wrote:
What's the recommended solution to such a problem, except adding
dependencies for all .c files which directly or indirectly include
`foo.h' (which is both inconvenient and error prone)?
Hi Werner,
I use line below in one of my project for similar t
On 09/04/2013 09:10 AM, Miles Bader wrote:
"Jeff Squyres (jsquyres)" writes:
We've been using sym links in the OMPI project for years in order to
compile a series of .c files in 2 different ways. It's portable to
all the places that we need/want it.
Hmm, how about just "cp" ...? :]
Autoconf
Hi automakers.
I have a test-suite (with automake parallel) in which some of the test
cases run multithreaded applications and therefore use eg four CPUs. In
order to avoid total overload I currently reduce number of jobs e.g.
'make -j2' rather than 'make -j8', which is sort of waste because i
On 06/06/2013 07:37 AM, Kip Warner wrote:
Hey list,
My make install target for my autotool'd project's translations
directory has a number of prerequisites. The one which seems to be
causing trouble is the install-data-yes target. Yes, I am aware the path
I am using contains spaces and yes I am
On 05/08/2013 02:12 AM, Rhys Ulerich wrote:
I gather that 'make install-strip' installs and then strips binaries.
Is there some variant that reverses the order? If not, any
recommendations for how to write one in an Automake-compliant manner?
Hi Rhys,
I'm tempted to believe the DESTDIR featu
On 2/7/13 7:58 PM, Stefano Lattarini wrote:
On 02/05/2013 12:22 AM, Peter Johansson wrote:
On 02/04/2013 11:31 PM, Stefano Lattarini wrote:
When I did this, I should really have published a 1.11.x release offering
this same option as well; that would have removed all confusion. Sigh,
such a
On 02/04/2013 11:31 PM, Stefano Lattarini wrote:
On 02/04/2013 01:16 AM, Luke Mewburn wrote:
[CUT]
Especially when the time between previous major releases was 2.5 years.
Examining the Changelog and release dates:
2009-12-08 Release automake 1.11.1
2012-02-21 Add "serial-tests" support
ould be removed with no loss:
2.0 -> 2.0
2.0.1 -> 2.1
2.0.2 -> 2.2
2.1 -> 3.0
3.0 -> 4.0
3.0.1 -> 4.1
4.0 -> 5.0
or just keep the scheme as is
1.14
1.14.1
1.14.2
1.15
1.16
1.16.1
1.17
Cheers,
Peter
--
Peter Johansson
er,
often have Automake fragments in a directory 'am/' which are included
into Makefile.am [in topdir]. For those fragment files, it would
probably be confusing if paths were inserted into variables. Perhaps one
could have a switch to turn that feature on.
Cheers,
Peter
--
Peter Johansson
0% happy with this solution though because it creates a
different dependency graph for maintainers and users similar to
AM_MAINTAINER_MODE.
Cheers,
Peter
--
Peter Johansson
On 10/31/2012 04:57 PM, Coly Li wrote:
Is there any method that I can add something into Makefile.am, so that the
generated Makefile can looks like:
--
foo_err.c foo_err.h: foo_err.et
compile_et prof_err.et
--
Sure add just that to Makefile.am and it should be
On 10/03/2012 02:15 PM, Sujit Devkar wrote:
Dear Sir/Madam,
I am working on a C++ project in which I am trying to use autotools to
make my project easy to deploy.
I have some .so files in a directory and some other files in different
directory.
Before using autotools, I had a shell script to i
On 9/30/12 8:27 PM, Peter Johansson wrote:
Any thoughts?
I should read the manual before making noise. Sorry.
http://www.gnu.org/software/automake/manual/automake.html#Errors-with-distclean
--
Peter Johansson
attempt, of course, I bumped into the problem
that the rule was triggered before 'bin/svndigest' was built. What is
the wisest solution for this problem? I can see that one could move the
rule out from 'make all' or that one have different rules depending on
building from VCS or tarball. Any thoughts?
Cheers,
Peter
--
Peter Johansson
Hi,
I just helped a co-developer who experienced a mysterious
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: configure.ac: adding subdirectory c++ to autoreconf
autoreconf: Entering
On 09/19/2012 04:23 PM, Vincent Torri wrote:
Hey
our documentation provides some images files in a subdirectory 'img'.
So, in EXTRA_DIST, we have added:
$(wildcard $(srcdir)/img/*.*)
automake reports that warning:
doc/Makefile.am:35: wildcard $(srcdir: non-POSIX variable name
doc/Makefile.am
Hi Eric,
On 08/07/2012 09:36 AM, Eric Blake wrote:
On 08/06/2012 05:29 PM, Peter Johansson wrote:
Hi,
I'd like to distinguish automake 1.11 from 1.12 (or later) at autoconf
time. I wonder is there's any documented macro that was introduced in
1.12 that I could use to m4_ifdef?
Hi,
I'd like to distinguish automake 1.11 from 1.12 (or later) at autoconf
time. I wonder is there's any documented macro that was introduced in
1.12 that I could use to m4_ifdef?
Cheers,
Peter
On 05/30/2012 02:09 AM, Adam Mercer wrote:
On Wed, May 23, 2012 at 6:13 PM, Peter Johansson wrote:
For me distcheck complains about no sed file which is because you call it
'sed -f git_version.sed' while it should be 'sed -f
$(srcdir)/git_version.sed' as the sed scrip
Hi Adam,
On 05/24/2012 02:59 AM, Adam Mercer wrote:
On Wed, May 23, 2012 at 10:03 AM, Adam Mercer wrote:
Is 'git_version.sed' intended to be distributed? If yes, you must place it in
EXTRA_DIST (and you have an usage error in that you've not done so).
Of course! Thanks, I imagined it'd be d
On 05/24/2012 02:59 AM, Adam Mercer wrote:
Hmm, distcheck is still complaining. I've attached a tarball
containing a striped down version of my project which illustrates the
problem. Can anyone see what I'm doing wrong?
Hi Adam,
For me distcheck complains about no sed file which is because y
Hello,
I find the recheck target very handy. In most projects we have a
recursive structure and added a
recheck: all
(cd test && make $@)
in top_dir. And typically I work like
edit sources
make recheck VERBOSE=1 -j8
edit source
etc
which works very nice. Now I've started to work in a pr
On 04/16/2012 06:52 AM, Dag-Erling Smørgrav wrote:
Is there a simple way to have automake install the same program under
multiple different names?
(the point being that the program behaves differently depending on the
name used to invoke it; bash and openssl are two examples of programs
which be
On 2/26/12 11:31 PM, Miles Bader wrote:
I think it's desirable that it "just work" wherever it gets installed,
and no matter who installs it (e.g. prefix=$HOME should work, and
shouldn't require setting LD_LIBRARY_PATH).
In my case it did work with prefix=$HOME because in that case -rpath was
s
Hi Miles,
On 2/26/12 9:47 PM, Miles Bader wrote:
But ... it doesn't seem to. Is something broken, is there an option I
should set... or?
On which system do you experience this? I've seen this problem on Fedora
and the problem was that the linker search path and the dynamic loader
search path
On 12/17/11 11:10 AM, Adam Mercer wrote:
On Sat, Dec 10, 2011 at 13:03, Stefano Lattarini
wrote:
Please report bugs and problems to, and send
general comments and feedback to.
On Mac OS X 10.7 (Lion)
All 826 tests behaved as expected (11 expected failures)
Similar on Mac OS 10.4:
==
On 11/30/11 11:11 AM, Joakim Tjernlund wrote:
Question: "make install" always install all targets, even if some of then
haven't been rebuilt
since last install. Is it possible to have some dependency sensitive install so
only rebuilt
targets are reinstalled?
Hi Jocke,
In one of my projects I
On 11/24/11 11:40 AM, Bob Friesenhahn wrote:
On Thu, 24 Nov 2011, Peter Rosin wrote:
There is one possibly hard bootstrapping problem. What if you want to
deploy some package that does not need a C compiler on some system that
lacks both a C compiler and GNU Make? You would have problems there
On 7/26/11 4:13 PM, myrdos2 wrote:
I have the following configure.ac file:
This is more of an Autoconf issue, so you may have better luck asking on
autoconf at...
# Checks for header files.
AC_CHECK_HEADERS_ONCE([boost/asio.hpp boost/bind.hpp boost/function.hpp
inttypes.h zlib.h])
Why not us
[removing automake-patches]
On 3/17/11 10:39 AM, Maynard Johnson wrote:
you aclocal calls. Also, in the next automake release, aclocal
will probably support a new 'ACLOCAL_PATH' environment variable
that would help solving this kind of problems
Well, you could always resort to adding proper
Hi Ralf,
On 2/13/11 3:32 AM, Ralf Wildenhues wrote:
Yep. I think that was one reason we explicitly documented the thing in
INSTALL. With this configuration, your preprocessor will be wrong
(because CFLAGS are not passed to it) which means macro values may be
computed wrongly.
I'm not sure I u
Thanks Ralf for your quick reply,
On 2/13/11 2:44 AM, Ralf Wildenhues wrote:
I would prepend all lines of a rule with a TAB, not just those not
following a backslash-escaped newline. I'm actually not totally sure
whether that was for portability to non-Posix make or so automake would
parse thin
Hello;
I got bitten by how VPATH builds work and wondered if there is a good
way to avoid getting bitten again.
I have an Automake snippet (see below) that creates a file, `.revision',
with current revision number and from this is a C header file
`revision.h' created. Then to test that thing
On 1/23/11 5:45 PM, Sergio Belkin wrote:
Hi,
How can I define an LDFLAGS once for all EXTRA_PROGRAMS, they are
around 20 and I am a bit lazy :) ?
Search for AM_LDFLAGS in the manual.
Cheers,
Peter
Hello,
The `INSTALL' file provided by autotools has the following blurp
On MacOS X 10.5 and later systems, you can create libraries and
executables that work on multiple system types--known as "fat" or
"universal" binaries--by specifying multiple `-arch' options to the
compiler but only a s
[adding automake @; replies can drop libtool @]
On 9/13/10 6:31 AM, Elvis Dowson wrote:
Elvis Dowson wrote:
I'm unable to build libtool as binary that includes both 32-bit and 64-bit
intel architecture on Mac OS X 10.6.4 using gcc-4.0.1, and get the
following error:
gcc-4.0: -E, -S, -save-t
Hi Sam,
On 7/3/10 6:52 PM, Sam Silla wrote:
TEST: simple_test
Looks like a typo; should it be "TESTS = simple_test"?
cheers,
Peter
On 6/20/10 2:56 PM, Wesley Smith wrote:
I've been looking through the automake docs trying to figure out how
to execute shell commands as part of the build process but before
anything actually gets compiled. Is this possible? I need this for
things like Qt's 'moc' and some other script-based co
On 6/20/10 11:59 AM, Bob Friesenhahn wrote:
My best guess is to add 'foreign' to AUTOMAKE_OPTIONS.
Not an option for a GNU package, I suppose.
Peter
Hello,
[adding automake; replies can drop bug-gsl]
This is
http://lists.gnu.org/archive/html/bug-gsl/2010-06/msg2.html
On 6/13/10 4:16 PM, Brian Gough wrote:
At Thu, 10 Jun 2010 22:16:58 -0400,
Peter Johansson wrote:
AFAIK there is no option in Automake to '--install'
Hi Patrick,
On 5/22/10 3:09 PM, Patrick Rutkowski wrote:
If I do "include_HEADERS = foo.h", then foo.h goes into, let's say,
/usr/local/include/foo.h
But can I instead make it go into /usr/local/include/some/arbitrary/path/foo.h?
I do:
include_foodir = $(includedir)/foo
include_foo_HEA
couple of accidents I decided to
remove the target.
Of note, GCS states that: "More generally, ‘make maintainer-clean’
should not delete anything that needs to exist in order to run configure
and then begin to build the program".
Cheers,
Peter
--
Peter Johansson
svndigest maintain
On 4/16/10 8:12 AM, Ole Tange wrote:
If any automake user would take the few minutes to help me write the
config files, it would be great. But a pointer to an exisiting simple
perl program using automake will also be appreciated.
Automake is perhaps not minimal, but it is an example of a p
siblings) are automatically distributed."
For the xxx.rc file, maybe the reason why it's distributed is because
I have xxx_la_SOURCES += xxx.rc in my Makefile.am?
exactly, so you could use 'nodist_xxx_la_SOURCES += xxx.rc'
Cheers,
Peter
--
Peter Johansson
svndigest maintainer, http://dev.thep.lu.se/svndigest
yat maintainer, http://dev.thep.lu.se/yat
anna accomplish. It makes it
easier for people to help.
Cheers,
Peter
--
Peter Johansson
svndigest maintainer, http://dev.thep.lu.se/svndigest
yat maintainer, http://dev.thep.lu.se/yat
Jef Driesen wrote:
On 12/04/10 14:59, Peter Johansson wrote:
Also, I would try avoid distributing
`version.h', but not sure how to do that from top of my head.
Why would you not distribute it?
Well, it's a matter of taste, but I see no real reason to include it in
the tarball.
Jef Driesen wrote:
mylib_la_SOURCES += version.c
mylib_HEADERS += version.h
BUILT_SOURCES = version.h
EXTRA_DIST += $(srcdir)/version
CLEANFILES += version-t
Took me a while to figure out the escaping of the @ symbol. It seems
to work fine, except that I would like to add "$(srcdir)/version.h.
Hi,
I've just upgraded one of my projects to automake 1.11 in order to use
the parallel-tests driver. Both the manual [1] and the Ralf's post here
[2] describes how to run the test suite lazily as
` make check RECHECK_LOGS='. My question is how it is determined which
tests are run in this case
On 4/2/10 7:04 AM, Jef Driesen wrote:
The problem I'm trying to solve is that I already have a version.h
that is generated from a version.h.in template that contains:
#define MYLIB_VERSION_MAJOR @MYLIB_VERSION_MAJOR@
#define MYLIB_VERSION_MINOR @MYLIB_VERSION_MINOR@
#define MYLIB_VERSION_MICR
going into:
/common/map.o
/linux/map.o
It is not clear what the conflict is here. Are you creating several
map.o files from the same map.cc? why?
Cheers,
Peter
--
Peter Johansson
svndigest maintainer, http://dev.thep.lu.se/svndigest
yat maintainer, http://dev.thep.lu.se/yat
Hi Jef,
On 3/17/10 8:23 AM, Jef Driesen wrote:
I only need it compiled into my library. The goal is that an
application using my library can report the exact revision of the
library (for diagnostic purpose).
With the solution I outlined in my previous posts, I can already get
the "normal" ve
On 3/16/10 8:29 AM, Jef Driesen wrote:
On 15/03/2010 22:18, Ralf Wildenhues wrote:
* Jef Driesen wrote on Sat, Mar 13, 2010 at 11:21:45PM CET:
I suppose you are referring to solutions like this:
m4_define([mylib_version_revision],m4_esyscmd([my_revision_script]))
where the revision script fe
Hi Ralf,
On 2/25/10 3:14 PM, Ralf Wildenhues wrote:
Changing that to 63 is probably a good idea (but we'd need to check
whether throughout autotools there is no expectance of the other value),
Is anyone more than autoreconf and the missing script calling automake
and thereby possibly react
y and convenience it would be nice if Automake also
returned 63 when an too old version was used. Is there any reason
against that or would a patch be welcome?
Thanks,
Peter
--
Peter Johansson
svndigest maintainer, http://dev.thep.lu.se/svndigest
yat maintainer, http://dev.thep.lu.se/yat
Hi,
Andreas Jellinghaus wrote:
Hi,
the combination autoconf/automake/libtool
makes it quite easy to create shared libraries.
but how can I install the file created as a single *.so
file, but without any *.la file etc.
the shared libraries we create implement a fixed plugin
interface thus they
Hi Andreas,
On 2/11/10 12:06 PM, Andreas Jellinghaus wrote:
also I wonder:
what about builddir vs. sourcedir? how do you handle that?
if people have a tar.gz with pre-build documentation, it
is in sourcedir. if people checkout svn and build in a seperate
build root, the documentation is created
m
in the build tree?
Cheers,
Peter
--
Peter Johansson
svndigest maintainer, http://dev.thep.lu.se/svndigest
yat maintainer, http://dev.thep.lu.se/yat
tools
generated Makefile and you realize you don't wanna see all that shell code.
When a developer asks for a silent build in order to catch problems
all one should see is real warnings and problems.
Have you tried Automake's silent-rules option?
Peter
--
Peter Johansson
svndi
is is a trivial problem but i cant seem to find
this in the manual.
please see here:
http://www.gnu.org/software/automake/manual/automake.html#Linking
http://www.network-theory.co.uk/docs/gccintro/gccintro_17.html
Cheers,
Peter
--
Peter Johansson
svndigest maintainer, http://dev.thep.
1 - 100 of 143 matches
Mail list logo
