2011-12-23 69 views
0

我试图在程序中嵌入这个'Makefile',所以我想出了如何,但我面临一个小问题。我的代码工作,如果我在Xcode的命令行工具中编程,但如果我选择使用SDL库编程它的应用程序,编译器剂量生成或导出(.o)文件..和链接器未能找到它们C-C++在程序中嵌入Makefile

我得到的错误是:品牌:GCC编译:没有这样的文件或目录 化妆: [main.o]错误1 *

通过右键点击的.app和选择View Package Contents,这是可以在里面运行的可执行文件,但是.app dosent。

,我的代码是:

char cmd[1040]; 
char cwd[1024]; 
char path[1024]; 
char path2[1024]; 
int status; 
FILE *fp; 

char *path = NULL; 
    size_t sizes; 
    path = getcwd(path, sizes); 
    cout << path << endl; 



    if (getcwd(cwd, sizeof(cwd)) != NULL) 
    { 
     snprintf(cmd, sizeof(cmd), "make -C \"%s\" flash", path); 

     // i = system(cmd); 


     /* Open the command for reading. */ 

     fp = popen(cmd, "r"); 

     if (fp == NULL) { 

      cout << ("Failed to run command\n"); 


     } 


     /* Read the output a line at a time - output it. */ // So we can use it later 

     while (fgets(path2, sizeof(path2)-1, fp) != NULL) { 

      printf("Info: %s\n", path2); 
     } 

     /* close */ 

     status = pclose(fp); 


    } 
  • 编译器Mac

http://www.obdev.at/products/crosspack/index.html

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 $< > [email protected] 


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


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

# asm from (hand coded) asm 
%.s: %.S 
    $(CC) -S $(ASMFLAGS) $< > [email protected] 


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



#### Generating object files #### 
# object from C 
.c.o: 
    $(CC) $(CFLAGS) -c $< -o [email protected] 


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

# object from asm 
.S.o : 
    $(CC) $(ASMFLAGS) -c $< -o [email protected] 


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

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


##### 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     ##### 
+0

在此代码中的位置是C++,如您的标记所承诺的那样? – 2011-12-23 12:14:11

+1

makefile支持C,C++,但我指的是使用C或C++的任何解决方案。 – John 2011-12-23 12:17:24

+0

C和C++是不同的语言。正确的C代码与正确的C++代码完全不同(请参阅单独的RAII和通用代码)。如果你买得起C++编译器,那么为什么不把C完全抛弃? – 2011-12-23 13:00:30

回答

0

一调试这种类型错误的可能方法是有一些方法将一些额外的标志传递给make,例如,

const char *makeflags = getenv("MYMAKEFLAGS"); 
    if (makeflags) 
     snprintf(cmd, sizeof(cmd), "make -C \"%s\" %s flash", path, makeflags); 
    else 
     snprintf(cmd, sizeof(cmd), "make -C \"%s\" flash", path); 

然后你(假设你的make是GNU MAKE)可以通过设置环境变量

export MYMAKEFLAGS=--debug=b 

调试你的事情,我会用patsubst GNU使函数来计算你的OBJDEPS这确实应该成为OBJFILES,例如

OBJFILES= \ 
     $(patsubst %.cc, %.o, $(CCFILES)) \ 
     $(patsubst %c, %.o, $(CFILES)) 
#etc 
+0

但是,先生,我如何植入“出口MYMAKEFLAGS = - 调试= B”?在我的源内? – John 2011-12-23 12:05:17

+0

你不把它放在你的源代码中。你只需在终端上输入它,然后再执行'make' – 2011-12-23 12:05:58

+0

的可执行文件。但是,先生,我试图自动执行该操作,而不是手动执行。 – John 2011-12-23 12:09:35