Re: Help with complex build

[Stephan Kulow <coolo@itm.mu-luebeck.de>]

> 
> 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.
> 
I don't think current automake supports this. For KDE we wrote a little
script that goes after automake over the Makefile.ins and looks for exactly
the same syntax you're describing. It basicly adds dependency rules and
calls to the (mico) idl compiler and adds an ImplRepo.o into the corrosponding
_OBJECTS list. 

If you want to take a look at it, you may find it on
http://kdecvs.stud.fh-heilbronn.de/cvsweb/kde-common/admin/am_edit

Greetings, Stephan

-- 
Stephan Kulow (coolo@kde.org)
detrever lleps ot ysae ylgnizama s'ti