avr-chat
[Top][All Lists]
Advanced

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

Re: [avr-chat] UISP / AVRDude : what to choose ?


From: David Kelly
Subject: Re: [avr-chat] UISP / AVRDude : what to choose ?
Date: Mon, 29 Aug 2005 18:52:28 -0500

On Sun, Aug 28, 2005 at 08:23:10PM -0400, Bob Paddock wrote:

On Sunday 28 August 2005 08:02 pm, Vincent Trouilliez wrote:


Maybe in a couple years, as the AVR and Linux community grows,
someone will start work on a full GUI IDE


Why would anyone what to destroy these excellent command line
tools by doing such a thing?  :-)

<sarcasm>
The obvious answer is that if its already good then its time to
handicap ourselves in order to compete on a level playing field.
Eliminate the advantage we have over GUI and overload the developer
with glitz, bells, and whistles, with a single unified
point-and-click development environment! We need to hide all our
configuration options in a binary project file under a GUI with
nested menus rather than a Makefile so only the original developer
has any idea (if he/she remembers) as to what is happening.

It seems to work for Microsoft, it must be right!

Not only Microsoft but Metrowerks CodeWarrior follows the same
model.

And so many ask for it, It Must Be Right(tm).
</sarcasm>

Seriously, I find myself thrown into an MC9S12NE64 project with
CodeWarrior. Example code such as Freescale OpenTCP doesn't load its
project file without warnings and errors. The latest version of CW
claims to be older than what was used to create the project in 2004.
Amazing.

Its less amazing after trying to compile the project after the load
errors. Many more warnings. Also missing a file.

Am guessing many options were reset when the CW versions didn't
match. That warnings and errors were muted by clicking a GUI option
rather than fix their very real causes.

These are the kind of problems I had with Microchip's MPLAB. At
least with the relatively small assembly projects one could hunt
down each and every option and override project settings from the
assembly file. That MPLAB was so stupid as to reference all files
with absolute paths, rendering a project which could not be moved in
the filesystem. That if archived *must* be restored in exactly the
same place, and MPLAB must also be installed in exactly the same
place as originally.

No, I am not interested in "enhancing" avr-gcc along those lines.
PN2 is just about right. Edit. Launch Make. Edit. Just about right.

--
David Kelly N4HHE, address@hidden
========================================================================
Whom computers would destroy, they must first drive mad.





reply via email to

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