>It does unfortunately look like you're invoking apxs in such a way as
to install two DSO's, not to link two pieces of object code into a
single DSO.
I tried to use the .la files (as you mentioned in a different message) as in:
apxs -i -n mod_fancy mod_fancy.la config.la
Unfortunately, apxs generated two .so files, mod_fancy.so and
config.so. It seems that apxs doesn't want to link multiple .la files
into one .so as it does if I passed it .cpp files.
I think that what I'm going to have to do is to create a single
library out of everything and then use apxs to install that. Anyone
have thoughts on that?
Huh. If you use the -c option correctly, ie., list all source code,
object files with one invocation of apxs then all the source file
object files, plus other object files, should be combined into one
loadable module at that point.
I see the problem now. You have:
%.o : %.cpp
apxs -S CC=g++ -c $<
which is just wrong. You shouldn't be calling apxs on each source file
separately. Instead do something like:
SRCS= mod_python.c _apachemodule.c requestobject.c tableobject.c util.c \
serverobject.c connobject.c filterobject.c hlist.c \
hlistobject.c finfoobject.c
mod_python.la: $(SRCS)
$(APXS) $(INCLUDES) -c $(SRCS) $(LDFLAGS) $(LIBS)
The name of the output module will use the basename of the first code
file listed in the list of source files in this case.
The problem is that I don't want apxs recompiling everything each
time I make a change. I'm looking at something like 100 files in the
total module.
--
Farokh
----------------------------------------------------------------------------
MCF Software...simply dependably engineered
Developers of ListSTAR http://www.liststar.com/, MacRADIUS
http://www.macradius.com/, Address List Sorter
http://www.mcfsoftware.com/als/, SimpleText Filter for EIMS
http://www.mcfsoftware.com/stf/ and Auto Reply plug-in for EIMS
http://www.mcfsoftware.com/ar/.
