[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Autoconf and nested projects
From: |
Pierre Mazi?re |
Subject: |
Autoconf and nested projects |
Date: |
Sat, 28 Dec 2002 18:46:18 +0100 (CET) |
Hello,
I have a project that uses a library using autoconf/automake/libtool.
so the directory structure of my project is:
/project
+-- configure.in
+-- Makefile.am
+-- configure
+-- /src
+-- Makefile.am
+-- foo.c
+-- /library
+-- configure.in
+-- Makefile.am
+-- configure
+-- /src
+-- Makefile.am
+-- bar.c
I'd like to keep the original library package without any modifications
In this original package, the library is build and installed as static
(libbar.a) and shared (libbar.so) libraries
In my project i would like to exclusively link my foo.o to the static
library bar.a and to void the library installation. But the autotools
always link foo.o with the shared lib. SO th esolution will be to pass the
--disbale-shared option to the library ./configure during the build
process
so here are ?y 2 questions:
1) how can i pass the --disable-shared option to the library ./configure
during th ebuild process of my project
2) how to avoid the library o be installed during my project installation
process
thanks for your solutions
- Autoconf and nested projects,
Pierre Mazi?re <=