Creating two libraries with same sourcefiles but diffrent defines

[Roesner Thomas]

Is seems that my posting yesterday had no text so next try:

Dear all,

i need some help for technical hitch.

I´d like to create a project (~ 30 subdirectories) with more than one library 
generated out of the same sourcefiles at the same time (no crosscompiler):

For example in directory av i´d like something like this:

libavstd_CFLAGS: -d NORMAL
libavstd_a_SOURCES: avbed.c avpub.c
libavstd_a_DEPENDENCIES: libavstd.a(avbed.c) libavstd.a(avpub.c)

libavpcl_CFLAGS: -d WITHPCL
libavpcl_a_SOURCES : avbed.c avpub.c
libavpcl_a_DEPENDENCIES: libavpcl.a(avbed.c) libavpcl.a(avpub.c)

where libavstd.a and libavpcl.a both depend on avbed.c and avpub.c, but they 
have diffrent compiler options.
If one of the sourcefiles has been changed, i need to start the compiler twice, 
with dependencies checked to the archive.
I´d like to remove the resulting *.o just after adding it to the library as you 
can see in the sniplet of the old makefile.

Using RANLIB results in "rm -f libavxxx.a" just after compiling the files

In my early makefile with only one compileroption it looked like this:

LIBOBJ =  libavstd.a(avbed.o) libavstd.a(avpub.o)

libavstd.a : $(LIBOBJ)
        $(AR) s libavstd.a

The rules looked like this: 

(%.o) : %.c
        $(CC) $(CFLAGS) -c $<
        $(AR) r $@ $*.o
        $(RM) -f $*.o

Is there any way to do this with automake/autoconf?

How can i configure different compileroptions for both targets, e.g. flags for 
debuging and profiling?

Can you please help me?

Thank you.

Kind regards
Thomas Roesner