This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Help with complex build
- To: automake@gnu.org
- Subject: Help with complex build
- From: othman@cs.wustl.edu
- Date: Sat, 26 Jun 1999 12:57:52 -0500 (CDT)
- Reply-To: othman@cs.wustl.edu
Hi,
I've been trying to migrate TAO over to automake but its current
makefiles rely heavily on GNU make extenesions, which I am trying to
avoid.
The current makefiles have something like this:
IDL_SRCS = ImplRepo ...etc...
TAO_ORBSVCS_SRCS += \
IOR_Multicast \
Naming/Naming_Context
IDL_FILES = \
$(addsuffix S, $(IDL_SRCS)) \
$(addsuffix C, $(IDL_SRCS))
FILES = $(IDL_FILES) $(TAO_ORBSVCS_SRCS)
DEFS = $(addsuffix .h,$(FILES))
LSRC = $(addsuffix .cpp,$(FILES))
Basically, ImplRepo.idl is compiled by the TAO IDL compiler into
several files: ImplRepo{S,C}.{h,cpp}, for example. Can anyone suggest
a way to compile the built sources without explicitly listing all of
them? The built sources will not be distributed with the distribution.
They will be built during each build. I ask since there are many IDL
source files. The lists that contains the built sources would be at
least four times as long as the IDL source list. It would be nice if I
could do what automake currently does with lex and yacc files, i.e.:
myprog_SOURCES = lexer.ll parser.yy foo.c bar.c
For example:
liborbsvcs_la_SOURCES = ImplRepo.idl IR_Helper.cpp ...etc...
Any ideas or suggestions? I'd really prefer not to have to explicitly
all of the generated sources since it would become a maintainer
nightmare.
Also, some of the sources are found in subdirectories (e.g.
Naming/NamingContext). What is a good strategy to compile the sources
in the subdirectories without having to resort to using VPATHs? The
objects in the subdirectories will be linked in to a shared library in
the directory containing the subdirectories.
Will the latest CVS automake help with any of the problems I described?
I realize that the directory structure I describe isn't very easy to
deal with. That may change in the future.
TIA,
-Ossama
--
Ossama Othman <othman@cs.wustl.edu>
Center for Distributed Object Computing, Washington University, St. Louis
58 60 1A E8 7A 66 F4 44 74 9F 3C D4 EF BF 35 88 1024/8A04D15D 1998/08/26