Make all the libgdb objects even when building gdb. This is because
cyscm links against ../../gdb/{...}.o Added a new target: libgdb-files. It creates a file of that name containing a list of files for libgdb. If the variable LIBGDBPREFIX is set, each file name has that prepended.
This commit is contained in:
parent
a13d789c7f
commit
8eb7b7c354
1 changed files with 12 additions and 1 deletions
|
@ -549,12 +549,23 @@ init.c: $(OBS) $(TSOBS)
|
|||
|
||||
.PRECIOUS: init.c
|
||||
|
||||
# The gdb target has two dependencies that aren't really
|
||||
# used when linking gdb. They are built for the sake of cyscm.
|
||||
|
||||
# Removing the old gdb first works better if it is running, at least on SunOS.
|
||||
gdb: $(OBS) $(TSOBS) $(ADD_DEPS) $(CDEPS) init.o
|
||||
gdb: $(OBS) $(TSOBS) $(ADD_DEPS) $(CDEPS) init.o libmain.o libutils.o
|
||||
rm -f gdb
|
||||
$(CC-LD) $(INTERNAL_LDFLAGS) -o gdb \
|
||||
init.o $(OBS) $(TSOBS) $(ADD_FILES) $(CLIBS) $(LOADLIBES)
|
||||
|
||||
LIBGDBFILES=$(LIBGDB_OBS) $(TSOBS) $(ADD_DEPS) $(CDEPS) init.o
|
||||
LIBGDBPREFIX=.
|
||||
libgdb-files: force_update
|
||||
-rm -f libgdb-files
|
||||
for i in $(LIBGDBFILES); do\
|
||||
echo ${LIBGDBPREFIX}/$$i >> libgdb-files;\
|
||||
done
|
||||
|
||||
libgdb.a: $(LIBGDB_OBS) $(TSOBS) $(ADD_DEPS) $(CDEPS) init.o
|
||||
rm -f libgdb.a
|
||||
$(AR) $(AR_FLAGS) libgdb.a $(LIBGDB_OBS) $(TSOBS) $(ADD_FILES) init.o
|
||||
|
|
Loading…
Reference in a new issue