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

[Torleif Sandnes]

> 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)

$(TARGET): $(OBJECTS)
         $(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 
"..\anotherfile.c"

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.

Torleif