[Anjuta-list] Anjuta for AVR embedded development

["Danail Nedyalkov" <duni bg googlemail com>]

Hi,

I'm currently using Eclipse with the avr-eclipse plugin for AVR
embedded development. I've tried to use Anjuta several times in the
past, but there were some key features missing, making the big
memory-eating full-of-features-that-I-don't-need Eclipse the better
choice. Well, you can clearly see why I don't like Eclipse in the
previous sentence and you can guess why I would like Anjuta.

However this time I got a little further with Anjuta and I decided to
discuss the features I miss. First of all, some basics about how I
make my projects: I create a simple Makefile-Project, replace the
default makefile with my avr template and go ahead with main.c and
hardware.h. In the most projects I have only 3-4 headers and c-files,
only when I use the avr usb driver from obdev.at I have a subfolder.
And I have no problem to type this information manually in the
Makefile, so far. There are some minor things, which can be automated
and included in some sort of anjuta-avr plugin, but this is not that
important for the start.

The basic two features I miss are at very first place the auto
completion in respect to the avr header files. Those headers are in
/usr/avr/include (like on the most distros). The avr-gcc compiler
already knows the paths and compiles everything correct. But it seems
that Anjuta isn't aware of that, and I haven't found a way to add it
manually. In practice I mean the following situation: When I insert
"#include <utils/delay.h>" in Eclipse I get auto completion when I
start typing "_delay_ms();". And when I click on the function I see
where it is included from. I guess this should be in the Symbols view
in Anjuta, and I should be able to click on the function and to be
refered to the delay.h file. This is an enormous advantage, especially
for the auto completion of the avr registers, pins and other macros
(#defines) in the avr include files - e.g. DDRB, PB4, TCCRA - one can
never be sure if one hasn't mistyped something or if this register was
preset on the target device, and it is a great help if this symbols
are shown in the Symbols view or when clicking on them with the mouse
(I don't know if this click-and-show behaviour is typical for Anjuta
or only for Eclipse).
The second basic feature concerns the Project view and the Makefile.
Basicly one sees all the targets of the Makefile in the Project view.
But when one clicks on them Anjuta tries to "open" the target,
whatever that means (I haven't figured that out). It's probably
reasonable for standard projects, but for avr Makefile projects the
targets are for example: uses (to burn the fuses), read_data (to
download the flash), flash (to burn the flash), etc. Currently I'm
"making" the targets from the terminal view in Anjuta. It would be
much better if Anjuta just executes "make target" when I click on that
target in the Project View. This will also spare additional taskbar
buttons to flash the device or to read the fuses, since one has only
to implement the "read_fuse" target and then just to double-click it
in the Project View.
If there is a way to get this two basic things working the way they
should for avrs in Anjuta that would be a great breaktrough for me,
and I'm sure for other avr developers. Then the minor things like
making an avr project template or a taskbar or even a menu for
additional features, like programmer choice, etc., can be easily done.

Thank you for taking some time to read my questions!

Best Regards,
Danail Nedyalkov