avrdude-dev
[Top][All Lists]
Advanced

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

Re: [avrdude-dev] avrdude on Windows


From: E. Weddington
Subject: Re: [avrdude-dev] avrdude on Windows
Date: Tue, 11 Feb 2003 13:36:12 -0700

On 11 Feb 2003 at 21:22, Joerg Wunsch wrote:

> [Do you need the Cc, or did you already subscribe?]

subscribed, thanks.
 
> As E. Weddington wrote:
> 
> > 1. Can GNU bison be used on all platforms and avrdude code written
> > for that?
> 
> Would be inconvenient for FreeBSD (bison is ported software, yacc is
> already part of the system), but i guess fixing the file so it works
> for bison could be done in a way where it doesn't break for [b]yacc.
> 
> ISTR that Ted already had a fix for this.

Got the message after I sent mine. Since I'm not even a beginner on 
yacc/bison, I'll leave this to experts.

 
> > Apparently when the built avrprog is executed it wants to find a
> > config file at /usr/local/avr/etc/avrprog.conf and it can't find it.
> > 
> > 2. Is this a fixed location that is looks for this config file?
> 
> It should be a configurable location.
> 
> > 3. If yes, can avrdude look in the current directory first?
> 
> Probably, but wouldn't it be more appropriate for Windows to have a
> registry entry for it, and an installer that creates (and later
> removes) that entry?  Just curious.  While it's almost always possible
> to find out the current directory, it's sometimes impossible to find
> the directory the program binary is located in (under Unix, there's
> not even a guarantee that this directory still exists -- the program
> binary could have been removed while the program is executing ;-),
> something that is impossible on Windows).
> 
> If at all, lookup in the current directory should only happen if it's
> running on Windows.  The Unix alternative (which is probably nice to
> have) would be to search $HOME for a file named .avrprog.conf or
> .avrprog.rc.

You're right of course, it shouldn't just look in the current 
directory. On Windows, the most common method is to search the 
current directory first, then the PATH. Would that be too uncommon on 
Unices?

I would prefer not having to set an additional environment variable, 
but it can be done if necessary. And same with a Windows registry 
entry; prefer not to, but it can be done.

Eric








reply via email to

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