Re: [Crash-utility] RFC: crash extension module handling

Anyway, I've been tinkering with the extensions/Makefile to do such a thing, and have a crude addition that does just that, although it does the compile of all "new" C files every time whether they need it or not -- via the additional "contrib" target: 30c30 < all: link_defs $(OBJECTS) --- > all: link_defs $(OBJECTS) contrib 43a44,50 > contrib: > @for CFILE in `/bin/ls *.c | grep -v echo.c | grep -v dminfo.c > | grep -v sial.c`; do \ > OUTPUT=`echo $$CFILE | cut -d. -f1`.so; \ > echo "gcc -nostartfiles -shared -rdynamic -o $$OUTPUT > $$CFILE -fPIC -D$(TARGET) $(TARGET_CFLAGS)"; \ > gcc -nostartfiles -shared -rdynamic -o $$OUTPUT $$CFILE > -fPIC -D$(TARGET) $(TARGET_CFLAGS); \ > done > It prevents the re-compilation of echo.c and dminfo.c, and of Luc Chouinard's upcoming sial.c extension module. (SIAL is an alternative crash extension mechanism -- more on that when it's available...) Anyway, I've tried screwing around with the Makefile to use a generic *.so target, using $@, $(basename ...) and so on, but I'm not a Makefile master, and I cannot quite get it quite right, although I'm sure it can be done. So if anybody out there can do it cleaner than the "contrib" target above, I'd like to take a look.