Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Message

RE: [AVR-Chat] AVR Studio 4 Build Issue

2012-07-06 by Cat C

AFAIK there MUST be a "avr32-gcc.exe" in there, along with many other exes... they are what do the work :-)Even 4.18 uses those, it's just that it selects them automagically when you check the box.
Cat

> To: AVR-Chat@yahoogroups.com
> From: wagnejam99@comcast.net
> Date: Fri, 6 Jul 2012 10:25:23 -0700
> Subject: Re: [AVR-Chat] AVR Studio 4 Build Issue
> 
> Cat -
> 
> I tried that and my download of WinAVR has no "avr-gcc" in "WinAVR-20100110\bin\". When I went back to 4.18, as I described in the just previous post, everything worked well.
> 
> Jim Wagner
> 
> On Jul 6, 2012, at 10:04 AM, Cat C wrote:
> 
> > 
> > On 4.19 ONLY (AFAIK) when you UNCHECK "Use AVR Toolchain" you have to actually browse to, and select the "other" "avr-gcc" and "make" executables in the boxes provided:
> > 
> > ...\WinAVR-20100110\bin\avr-gcc.exe...\WinAVR\WinAVR-20100110\utils\bin\make.exe 
> > 
> > Then you can build using your "winavr" included build tools.
> > Cat
> > 
> > > To: AVR-Chat@yahoogroups.com
> > > From: englsprogeny1@yahoo.com
> > > Date: Fri, 6 Jul 2012 16:24:35 +0000
> > > Subject: [AVR-Chat] AVR Studio 4 Build Issue
> > > 
> > > 
> > > AVR Studio Version 4.19
> > > Build 730
> > ... 
> > 
> > > When I un-select this and point to my GCC.exe file I am unable to build. 'no build tools defined'
> > > 
> > > If I use my own makefile and other files I am able, of course, to do builds.
> > > 
> > > 
> > > 
> > > Many thanks for any input
> > > 
> > 
> > 
> > 
> > [Non-text portions of this message have been removed]
> > 
> > 
> 
> 
> 
> [Non-text portions of this message have been removed]
> 
> 
> 
> ------------------------------------
> 
> Yahoo! Groups Links
> 
> 
> 
 		 	   		  

[Non-text portions of this message have been removed]

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.