User forums > Embedded development

a problem compiling eeprom of avr(atmega16,winavr) program

<< < (5/7) > >>

scarphin:
After further tweaking I think I've found the reason. I had the '$winavr/avr/lib' folder in the 'search directories' for the linker. When this is removed, linker finds the correct 'libc.a' somehow and everything builds ok. Aelxx's configuration doesn't have this folder included that was the reason he didn't have linker problems. I'm not sure if it's CB or me added this folder in the 'linker search dirs' but if it is CB, it shouldn't do it anymore for the avr-gcc. Shoud I make a bug report about this?

zage2009:
I reinstall cb10.05 and WinAVR-20100110 in  windows xp and windows7 which are installed in vmware Workstation and I find that in winxp there still is the '$winavr/avr/lib' folder in the 'search directories' for the linker,but in win7  the 'search directories' for the linker is empty and everything builds ok.I guess that Aelxx probably uses CB and WinAVR in win7.Just the difference between the operating system causes the problem?

scarphin:
Did u also delete the CB settings in the 'C:\Documents and Settings\$user$\Application Data\codeblocks' folder when reinstalling on XP? Those are the settings CB uses when launched. But afaik CB adds the folders 'avr/include/' and 'avr/lib/'. From what it seems the latter shouldn't be added. The reason that these are not added on Win7 might be something else. Can any dev help us out here pls?

Aelxx:
scarphin - Glad you found your problem's solution.
Zage2009 - No. I use WinXP SP3, C::B rev6454 or Later. I keep my old C::B configurations after reinstalling C::B. And also after reinstalling winAvr I always do manual compiler configuration in C::B, cause C::B doesn't autodetect avr-gcc (IMHO), maybe at this step I remove '$winavr/avr/lib' - can't say, cause I don't remember. Guess scarphin is right and it's some C::B's AVR-GCC compiler configuration bug, and I was lucky not to hit it  :D

Jenna:

--- Quote from: Aelxx on August 12, 2011, 09:45:19 am ---scarphin - Glad you found your problem's solution.
Zage2009 - No. I use WinXP SP3, C::B rev6454 or Later. I keep my old C::B configurations after reinstalling C::B. And also after reinstalling winAvr I always do manual compiler configuration in C::B, cause C::B doesn't autodetect avr-gcc (IMHO), maybe at this step I remove '$winavr/avr/lib' - can't say, cause I don't remember. Guess scarphin is right and it's some C::B's AVR-GCC compiler configuration bug, and I was lucky not to hit it  :D

--- End quote ---

Thes settings are made if you use autodetection, otherwise they stay empty.

Navigation

[0] Message Index

[#] Next page

[*] Previous page