[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] Cygwin paths causes problems for AVR Studio

From: Torleif Sandnes
Subject: Re: [avr-gcc-list] Cygwin paths causes problems for AVR Studio
Date: Mon, 04 Jul 2005 08:52:38 +0200
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

I've had to switch from WinAVR to Cygwin built tools as I need to compile for the ATMega325 which isn't support under the current windows toolset. My problem is that I would like to continue using AVR Studio for debugging but cygwin inserts its path names (/cygdrive/c/..... ) into the ELF and subsequently my extended COFF has these paths which AVR Studio can't decipher.

One solution may be to rewrite your makefile to use relative paths.
Like this:

OBJECTS=testVisibility.o anotherfile.o

SOURCES=../testVisibility.c ../anotherfile.c

all: $(TARGET)

         $(CC) $(CFLAGS) $(LDFLAGS) $(OBJECTS) $(LIBDIRS) $(LIBS) -o $(TARGET)

testVisibility.o: ..\testVisibility.c
$(CC) $(INCLUDES) $(CFLAGS) -c -Wall -gdwarf-2 -o testVisibility.o "..\testVisibility.c"

anotherfile.o: ..\anotherfile.c
        $(CC) $(INCLUDES) $(CFLAGS) -c  -Wall -gdwarf-2 -o anotherfile.o 

The elf/dwarf parser has code in it to handle the cygwin prefix, but this has probably not been properly tested. I will add it to my buglist.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]