Shell/Makefile链接器

Question

我已经下载了makefile，并且正在用xcode中的C/C++代码运行它。

它的工作原理和输出信息（在控制台模式下），但是当我在做应用程序（使用GUI），它说：

 
**make: avr-gcc: No such file or directory 

make: *** [main.o] Error 1** 

我跑这样的：

snprintf(cmd, sizeof(cmd), "make -C \"%s/System/\" flash", path); 

etc ..但编译器不生成/导出（.o）文件，所以链接器无法找到它们。

The makefile is：

######### AVR Project Makefile Template ######### 
######          ###### 
###### Copyright (C) 2003-2005,Pat Deegan, ###### 
######   Psychogenic Inc    ###### 
######   All Rights Reserved   ###### 
######          ###### 
###### You are free to use this code as part ###### 
###### of your own applications provided  ###### 
###### you keep this copyright notice intact ###### 
###### and acknowledge its authorship with ###### 
###### the words:        ###### 
######          ###### 
###### "Contains software by Pat Deegan of ###### 
###### Psychogenic Inc (www.psychogenic.com)" ###### 
######          ###### 
###### If you use it as part of a web site ###### 
###### please include a link to our site,  ###### 
###### http://electrons.psychogenic.com or ###### 
###### http://www.psychogenic.com    ###### 
######          ###### 
#################################################### 


##### This Makefile will make compiling Atmel AVR 
##### micro controller projects simple with Linux 
##### or other Unix workstations and the AVR-GCC 
##### tools. 
##### 
##### It supports C, C++ and Assembly source files. 
##### 
##### Customize the values as indicated below and : 
##### make 
##### make disasm 
##### make stats 
##### make hex 
##### make writeflash 
##### make gdbinit 
##### or make clean 
##### 
##### See the http://electrons.psychogenic.com/ 
##### website for detailed instructions 


#################################################### 
#####           ##### 
#####    Configuration    ##### 
#####           ##### 
##### Customize the values in this section for ##### 
##### your project. MCU, PROJECTNAME and  ##### 
##### PRJSRC must be setup for all projects, ##### 
##### the remaining variables are only   ##### 
##### relevant to those needing additional  ##### 
##### include dirs or libraries and those  ##### 
##### who wish to use the avrdude programmer ##### 
#####           ##### 
##### See http://electrons.psychogenic.com/ ##### 
##### for further details.      ##### 
#####           ##### 
#################################################### 


#####   Target Specific Details   ##### 
#####  Customize these for your project  ##### 

# Name of target controller 
# (e.g. 'at90s8515', see the available avr-gcc mmcu 
# options for possible values) 
MCU=atmega8 

# id to use with programmer 
# default: PROGRAMMER_MCU=$(MCU) 
# In case the programer used, e.g avrdude, doesn't 
# accept the same MCU name as avr-gcc (for example 
# for ATmega8s, avr-gcc expects 'atmega8' and 
# avrdude requires 'm8') 
PROGRAMMER_MCU=m8 

# Name of our project 
# (use a single word, e.g. 'myproject') 
PROJECTNAME=myproject 

# Source files 
# List C/C++/Assembly source files: 
# (list all files to compile, e.g. 'a.c b.cpp as.S'): 
# Use .cc, .cpp or .C suffix for C++ files, use .S 
# (NOT .s !!!) for assembly source code files. 
PRJSRC=main.c myclass.cpp lowlevelstuff.S 

# additional includes (e.g. -I/path/to/mydir) 
INC=-I/path/to/include 

# libraries to link in (e.g. -lmylib) 
LIBS= 

# Optimization level, 
# use s (size opt), 1, 2, 3 or 0 (off) 
OPTLEVEL=s 


#####  AVR Dude 'writeflash' options  ##### 
##### If you are using the avrdude program 
##### (http://www.bsdhome.com/avrdude/) to write 
##### to the MCU, you can set the following config 
##### options and use 'make writeflash' to program 
##### the device. 


# programmer id--check the avrdude for complete list 
# of available opts. These should include stk500, 
# avr910, avrisp, bsd, pony and more. Set this to 
# one of the valid "-c PROGRAMMER-ID" values 
# described in the avrdude info page. 
# 
AVRDUDE_PROGRAMMERID=stk500 

# port--serial or parallel port to which your 
# hardware programmer is attached 
# 
AVRDUDE_PORT=/dev/ttyS1 


#################################################### 
#####    Config Done    ##### 
#####           ##### 
##### You shouldn't need to edit anything  ##### 
##### below to use the makefile but may wish ##### 
##### to override a few of the flags   ##### 
##### nonetheless        ##### 
#####           ##### 
#################################################### 


##### Flags #### 

# HEXFORMAT -- format for .hex file output 
HEXFORMAT=ihex 

# compiler 
CFLAGS=-I. $(INC) -g -mmcu=$(MCU) -O$(OPTLEVEL) \ 
    -fpack-struct -fshort-enums    \ 
    -funsigned-bitfields -funsigned-char \ 
    -Wall -Wstrict-prototypes    \ 
    -Wa,-ahlms=$(firstword     \ 
    $(filter %.lst, $(<:.c=.lst))) 

# c++ specific flags 
CPPFLAGS=-fno-exceptions    \ 
    -Wa,-ahlms=$(firstword   \ 
    $(filter %.lst, $(<:.cpp=.lst))\ 
    $(filter %.lst, $(<:.cc=.lst)) \ 
    $(filter %.lst, $(<:.C=.lst))) 

# assembler 
ASMFLAGS =-I. $(INC) -mmcu=$(MCU)  \ 
    -x assembler-with-cpp   \ 
    -Wa,-gstabs,-ahlms=$(firstword \ 
     $(<:.S=.lst) $(<.s=.lst)) 


# linker 
LDFLAGS=-Wl,-Map,$(TRG).map -mmcu=$(MCU) \ 
    -lm $(LIBS) 

##### executables #### 
CC=avr-gcc 
OBJCOPY=avr-objcopy 
OBJDUMP=avr-objdump 
SIZE=avr-size 
AVRDUDE=avrdude 
REMOVE=rm -f 

##### automatic target names #### 
TRG=$(PROJECTNAME).out 
DUMPTRG=$(PROJECTNAME).s 

HEXROMTRG=$(PROJECTNAME).hex 
HEXTRG=$(HEXROMTRG) $(PROJECTNAME).ee.hex 
GDBINITFILE=gdbinit-$(PROJECTNAME) 

# Define all object files. 

# Start by splitting source files by type 
# C++ 
CPPFILES=$(filter %.cpp, $(PRJSRC)) 
CCFILES=$(filter %.cc, $(PRJSRC)) 
BIGCFILES=$(filter %.C, $(PRJSRC)) 
# C 
CFILES=$(filter %.c, $(PRJSRC)) 
# Assembly 
ASMFILES=$(filter %.S, $(PRJSRC)) 


# List all object files we need to create 
OBJDEPS=$(CFILES:.c=.o) \ 
    $(CPPFILES:.cpp=.o)\ 
    $(BIGCFILES:.C=.o) \ 
    $(CCFILES:.cc=.o) \ 
    $(ASMFILES:.S=.o) 

# Define all lst files. 
LST=$(filter %.lst, $(OBJDEPS:.o=.lst)) 

# All the possible generated assembly 
# files (.s files) 
GENASMFILES=$(filter %.s, $(OBJDEPS:.o=.s)) 


.SUFFIXES : .c .cc .cpp .C .o .out .s .S \ 
    .hex .ee.hex .h .hh .hpp 


.PHONY: writeflash clean stats gdbinit stats 

# Make targets: 
# all, disasm, stats, hex, writeflash/install, clean 
all: $(TRG) 

disasm: $(DUMPTRG) stats 

stats: $(TRG) 
    $(OBJDUMP) -h $(TRG) 
    $(SIZE) $(TRG) 

hex: $(HEXTRG) 


writeflash: hex 
    $(AVRDUDE) -c $(AVRDUDE_PROGRAMMERID) \ 
    -p $(PROGRAMMER_MCU) -P $(AVRDUDE_PORT) -e  \ 
    -U flash:w:$(HEXROMTRG) 

install: writeflash 

$(DUMPTRG): $(TRG) 
    $(OBJDUMP) -S $< > $@ 


$(TRG): $(OBJDEPS) 
    $(CC) $(LDFLAGS) -o $(TRG) $(OBJDEPS) 


#### Generating assembly #### 
# asm from C 
%.s: %.c 
    $(CC) -S $(CFLAGS) $< -o $@ 

# asm from (hand coded) asm 
%.s: %.S 
    $(CC) -S $(ASMFLAGS) $< > $@ 


# asm from C++ 
.cpp.s .cc.s .C.s : 
    $(CC) -S $(CFLAGS) $(CPPFLAGS) $< -o $@ 



#### Generating object files #### 
# object from C 
.c.o: 
    $(CC) $(CFLAGS) -c $< -o $@ 


# object from C++ (.cc, .cpp, .C files) 
.cc.o .cpp.o .C.o : 
    $(CC) $(CFLAGS) $(CPPFLAGS) -c $< -o $@ 

# object from asm 
.S.o : 
    $(CC) $(ASMFLAGS) -c $< -o $@ 


#### Generating hex files #### 
# hex files from elf 
##### Generating a gdb initialisation file ##### 
.out.hex: 
    $(OBJCOPY) -j .text     \ 
     -j .data      \ 
     -O $(HEXFORMAT) $< $@ 

.out.ee.hex: 
    $(OBJCOPY) -j .eeprom     \ 
     --change-section-lma .eeprom=0 \ 
     -O $(HEXFORMAT) $< $@ 


##### Generating a gdb initialisation file ##### 
##### Use by launching simulavr and avr-gdb: ##### 
##### avr-gdb -x gdbinit-myproject   ##### 
gdbinit: $(GDBINITFILE) 

$(GDBINITFILE): $(TRG) 
    @echo "file $(TRG)" > $(GDBINITFILE) 

    @echo "target remote localhost:1212" \ 
         >> $(GDBINITFILE) 

    @echo "load"  >> $(GDBINITFILE) 
    @echo "break main" >> $(GDBINITFILE) 
    @echo "continue" >> $(GDBINITFILE) 
    @echo 
    @echo "Use 'avr-gdb -x $(GDBINITFILE)'" 


#### Cleanup #### 
clean: 
    $(REMOVE) $(TRG) $(TRG).map $(DUMPTRG) 
    $(REMOVE) $(OBJDEPS) 
    $(REMOVE) $(LST) $(GDBINITFILE) 
    $(REMOVE) $(GENASMFILES) 
    $(REMOVE) $(HEXTRG) 



#####     EOF     ##### 

Answer 1

像

avr-gcc: No such file or directory 

错误消息表示的几件事情

1. 可执行avr-gcc 1未安装（正确）

2. 和/或PATH env var不包含保存可执行文件的目录

3. makefile被错误地调用。

4. 其他

这里有一些事情要尝试

当你说“下载的生成文件”，这就是你下载的，还是你下载一个完整的软件包（AVR？）如果只是makefile，你必须先下载整个软件包，然后才能继续。

许多软件包依靠自动捕获的设置信息或作为env-vars传递到运行make文件。

查看软件分发附带的.txt文件（有时是.doc）。寻找README或INSTALL。您可能会发现需要运行一组简单的命令来设置环境。很经常

./configure 
make 
make install 

是你所需要的。

如果有这样的产品包装中没有方向，那么你需要发现您的AVR-GCC位于并添加到PATH，即

find/-name 'avr-gcc*' 

以通过返回的路径，剥离结束/avr-gcc并将其添加到您的路径，即

PATH="${PATH}:/path/to/avr-gcc-subdir" 
export PATH 
make 

如果这不起作用，请编辑您的问题，包括一个URL来为这个包的源代码。

我希望这会有所帮助。

P.S.请记住通过按复选标记http://i.imgur.com/uqJeW.png来接受最能解决您问题的答案（如果有的话）。当你看到好的Q & A时，使用灰色三角形http://i.imgur.com/kygEP.png对它们进行投票。请注意，向其他人授予声誉点并不意味着对声望点的扣除（除非您已发布奖励）。