Attachment 3274 Details for Bug 4299 – Corrected makefile

Corrected makefile

Makefile (text/plain), 1.40 KB, created by Alexey Shabalin on 2005-09-15 00:16:26 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alexey Shabalin

Created: 2005-09-15 00:16:26 UTC

Size: 1.40 KB

patch

obsolete

># Copyright (c) 1999-2005
># Motorola, Inc., ALL RIGHTS RESERVED
>
>SOURCES := \
>	CairoTest.cpp
>	
>
>OBJECTS := $(SOURCES:.cpp=.o)
>
>
>PKG_CONFIG_PATH=/opt/cairo-head/lib/pkgconfig
>CC =/usr/bin/g++
>CFLAGS =   `pkg-config --cflags libsvg-cairo`
>LIB_PATH = `pkg-config --libs libsvg-cairo`
>
>LIBS =     -lcairo -lsvg-cairo
>
>DFLAGS = -g
>DEFINES = -DLINUX  
>
>DESTDIR = .
>#
>###############################################
>
>#
># Clear the vpath
>#
>vpath %.cpp
>vpath %.h
>vpath %.hpp
>vpath %.d
>vpath %.o
>
>#
># Set the vpath
>#
>vpath %.cpp .
>vpath %.d .
>vpath %.o .
>
>
>all: $(OBJECTS)
>#	quantify $(CC) $(DFLAGS) $(DEFINES) $(CFLAGS) -g -o MyTest *.o $(LIB_PATH) $(LIBS)
>#	purify $(CC) $(DFLAGS) $(DEFINES) $(CFLAGS) -g -o MyTest *.o $(LIB_PATH) $(LIBS)
>	$(CC) $(DFLAGS) $(DEFINES) $(CFLAGS) -g -o MyTest *.o $(LIB_PATH) $(LIBS)
>
>#
># Create a rule to build dependency files
># (straight from the Make online manual)
>#
>%.d: %.cpp
>	@echo "Creating dependency file $(notdir $@)"
>	@"$(SHELL)" -ec '$(CC) $(DFLAGS) $(DEFINES) $(CFLAGS) -MM $< ' > ./$@
>
>#
># Include all the dependency files.  The - is so that we don't see warnings
># about the file not existing.  When this happens the depend rule is kicked
># to create it.
>#
>ifneq ($(MAKECMDGOALS), clean)
>DFILES = $(SOURCES:.cpp=.d)
>
>-include ./$(DFILES) 
>endif
>
>#
>#
>#
>%.o: %.cpp
>	@echo "Compiling $(notdir $@)"
>	@$(CC) -g -c $(DFLAGS) $(DEFINES) $(CFLAGS) -o ./$(notdir $@) $<
>
>
>
>#
>#
>#
>clean:
>	@rm -f *.[od] *.so
>

Actions: View

Attachments on bug 4299: 3146 | 3147 | 3148 | 3202 | 3243 | 3253 | 3254 | 3260 | 3261 | 3274 | 3275

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.