view console/Makefile @ 13905:4e44ecb866bd

[gaim-migrate @ 16394] msn_session_sync_users() iterates over the buddy list, following the ->next pointers of the groups, contacts, and buddies. msn_show_sync_issue(), if called, removed the buddy for which it was called, in preparation for the buddy either being added to the server list or confirmed-to-be-removed. This could lead to the buddy pointer being released and ->next therefore being junk. The buddy is now not removed until the user responds to the action dialog presented via msn_show_sync_issue(). I'm unclear why gtkgaim got away with this exercise in memory stomping but Adium/libgaim crashed every time, but it's safer in any case. I also changed some foo->bar to gaim_foo_get_bar(). committer: Tailor Script <[e-mail]>

CC=gcc
CFLAGS=`pkg-config --cflags gaim gobject-2.0 gnt` -g -Wall
LDFLAGS=`pkg-config --libs gaim gobject-2.0 libxml-2.0 gnt` -pg

GG_SOURCES = \
	gntblist.c \
	gntconv.c \
	gntui.c

GG_HEADERS = \
	gntblist.h \
	gntconv.h \
	gntui.h

GG_OBJECTS = \
	gntblist.o \
	gntconv.o \
	gntui.o

all: gntgaim

gntgaim: gntgaim.o $(GG_OBJECTS)
	$(CC) -o gntgaim gntgaim.o $(GG_OBJECTS) $(LDFLAGS)
gntblist.o: gntblist.c $(GG_HEADERS)
gntconv.o: gntconv.c $(GG_HEADERS)
gntgaim.o: gntgaim.c gntgaim.h $(GG_HEADERS)
gntui.o: gntui.c $(GG_HEADERS)

clean:
	rm -f *.o
	rm -f gntgaim