9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Heyas
I'm trying to rewrite the install procedure of TUI, applying the standards of the Autotools.
Inofficial:
unix - Why always ./configure; make; make install; as 3 seperate steps? - Stack Overflow
autoconf automake tutorial
Official:
... (4 Replies)
Discussion started by: sea
4 Replies
2. Programming
Hi,
I'm trying to make my source "buildable". autoconf and automake tools are used. configure and Makefile.in files are created successfully.
configure.ac:
AC_INIT()
AC_CONFIG_SRCDIR()
AC_PROG_CXX
AM_INIT_AUTOMAKE(main, 0.1)
AC_CHECK_HEADERS()... (0 Replies)
Discussion started by: Vourhey
0 Replies
3. Shell Programming and Scripting
hi,
I have written the Makefile.am and autoconf.ac files and am looking to build my project by providing the following commands:
$autoreconf -f -i -m
$./configure
both of the above work fine, but when I give the make command, I get the following error:
make all-am
make: Entering directory... (0 Replies)
Discussion started by: bacpp
0 Replies
4. Shell Programming and Scripting
hi all,
I have written a simple C program hello.c and a Makefile.ac but when i try to run automake it does not create Makefile.in hence I am not able to run ./configure command in my directory. Following are the containts of my prog.
hello.c
--------
Code:
#include<stdio.h>
main()
{... (0 Replies)
Discussion started by: useless79
0 Replies
5. UNIX for Advanced & Expert Users
Hi,
I'm on Fedora-11-x86_64 with KDevelop 3.5.4. I have automake 1.11 installed, but when I attempt to run automake and friends on a new project I get:
*** YOU'RE USING automake (GNU automake) 1.11
*** KDE requires automake 1.6.1 or newer
I reported(KDevelop) the error Bug: 210084 ... (11 Replies)
Discussion started by: lucelio
11 Replies
6. BSD
Hi gurus,
I'm a FreeBSD noob who has generated an error, searched everywhere for solutions, and has just joined this forum (and searched it) hoping you can help.
I really need to get mysql server installed again ASAP, and preferably with Sphinx as a storage engine, or my web app in dev is... (2 Replies)
Discussion started by: userunx
2 Replies
7. Programming
I am using the GNU automake.
I have created the Configure.in and Makefile.am files but don't know how to link in my dependencies.
I have basically added another project (OpenCV) to my eclipse workspace and want to reference this in the build. I have set Eclipse up to include the Cpp files... (5 Replies)
Discussion started by: hembergb
5 Replies
8. UNIX for Dummies Questions & Answers
helo , i m using RHEL 4 and in that automake -2.59
now i install automake-2.61
but when i say # rpm -qa |grep automake
it shows only automake-2.59
actually i want to use automake-2.61
so how to resolve this issue
amit (5 Replies)
Discussion started by: amitpansuria
5 Replies
9. UNIX for Advanced & Expert Users
hi
on machine automake 1.9 are install but i am not able create make file
so please tell me what proper command to create make file using automake (1 Reply)
Discussion started by: munnu
1 Replies
AUTOMAKE(1) General Commands Manual AUTOMAKE(1)
NAME
automake - automatically create Makefile.in's from Makefile.am's
SYNOPSIS
automake [ -a | --add-missing ] [ --amdir=DIR ] [ --build-dir=DIR ] [ -c | --copy ] [ --cygnus ] [ -f | --force-missing ] [ --foreign ] [
--gnits ] [ --gnu ] [ --help ] [ -i | --ignore-deps ] [ --include-deps ] [ --no-force ] [ -o DIR ] [ --output-dir=DIR ] [ --srcdir-name=DIR
] [ -v | --verbose ] [ --version ] [ --Werror | --Wno-error ]
DESCRIPTION
To create all the Makefile.ins for a package, run the automake program in the top level directory, with no arguments. automake will auto-
matically find each appropriate Makefile.am (by scanning configure.in) and generate the corresponding Makefile.in. Note that automake has
a rather simplistic view of what constitutes a package; it assumes that a package has only one configure.in, at the top. If your package
has multiple configure.ins, then you must run automake in each directory holding a configure.in.
You can optionally give automake an argument; .am is appended to the argument and the result is used as the name of the input file. This
feature is generally only used to automatically rebuild an out-of-date Makefile.in. Note that automake must always be run from the topmost
directory of a project, even if being used to regenerate the Makefile.in in some subdirectory. This is necessary because automake must
scan configure.in, and because automake uses the knowledge that a Makefile.in is in a subdirectory to change its behavior in some cases.
automake accepts the following options:
-a
--add-missing
Automake requires certain common files to exist in certain situations; for instance config.guess is required if configure.in runs
AC_CANONICAL_HOST. Automake is distributed with several of these files; this option will cause the missing ones to be automatically
added to the package, whenever possible. In general if Automake tells you a file is missing, try using this option. By default
Automake tries to make a symbolic link pointing to its own copy of the missing file; this can be changed with --copy.
--libdir=DIR
Look for Automake data files in directory DIR instead of in the installation directory. This is typically used for debugging.
-c
--copy When used with --add-missing, causes installed files to be copied. The default is to make a symbolic link.
--cygnus
Causes the generated Makefile.ins to follow Cygnus rules, instead of GNU or Gnits rules.
-f
--force-missing
When used with --add-missing, causes standard files to be rebuilt even if they already exist in the source tree. This involves
removing the file from the source tree before creating the new symlink (or, with --copy, copying the new file).
--foreign
Set the global strictness to foreign.
--gnits
Set the global strictness to gnits.
--gnu Set the global strictness to gnu. This is the default strictness.
--help Print a summary of the command line options and exit.
-i
--ignore-deps
This disables the dependency tracking feature.
--include-deps
This enables the dependency tracking feature. This feature is enabled by default. This option is provided for historical reasons
only and probably should not be used.
--no-force
Ordinarily automake creates all Makefile.ins mentioned in configure.in. This option causes it to only update those Makefile.ins
which are out of date with respect to one of their dependents.
-o DIR
--output-dir=DIR
Put the generated Makefile.in in the directory DIR. Ordinarily each Makefile.in is created in the directory of the corresponding
Makefile.am. This option is used when making distributions.
-v
--verbose
Cause Automake to print information about which files are being read or created.
--version
Print the version number of Automake and exit.
--Werror
--Wno-error
--Werror will cause all warnings issued by automake to become errors. Errors affect the exit status of automake, while warnings do
not. --Wno-error, the default, causes warning to be treated as warnings only.
SEE ALSO
aclocal(1), and the Texinfo documentation for automake
AUTHORS
Automake was written primarily by David Mackenzie and Tom Tromey. This manpage written by Ben Pfaff <pfaffben@pilot.msu.edu> for the
Debian GNU/Linux automake package.
28 Jan 2002 AUTOMAKE(1)