This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
I cant get my ./configure to use the arm-linux-gcc (and so on), it keeps using the gcc whatever I try to do.
Traditionally, one does this in one of two ways: a) ./configure --target arm-linux (which causes CC to default to arm-linux-gcc, I think) b) CC=arm-linux-gcc ./configure (which sets CC directly)
the intent is to make things portable, so the builder can always pick a different CC or target.
Regards Robert Staven
------------------------------------------------------- # Set target prefix for tool chain e.g. arm-linux-gcc TARGET = arm-linux- #TARGET =
# Tool names CC = $(TARGET)gcc export CC
# Build settings CFLAGS = `$(TARGET)pkg-config gtk+-2.0 --cflags` LDFLAGS = `$(TARGET)pkg-config gtk+-2.0 --libs`
# Installation variables EXEC_NAME = hello
# Files needed for the build OBJS = hello.o
# Make rules all: hello
hello: $(OBJS) $(CC) -o $(EXEC_NAME) $(OBJS) $(LDFLAGS) $(TARGET)strip $(EXEC_NAME)
clean: rm -f *.o $(EXEC_NAME) core
distclean: rm -f *~ rm -f *.o $(EXEC_NAME) core
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |