httpd-modules-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Farokh Irani <>
Subject Re: APXS question
Date Mon, 23 Jul 2007 19:54:46 GMT
>>  >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
>>Unfortunately, apxs generated two .so files, and
>> 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
> $(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.

MCF Software...simply dependably engineered
Developers of ListSTAR, MacRADIUS, Address List Sorter, SimpleText Filter for EIMS and Auto Reply plug-in for EIMS

View raw message