Re: [anjuta-devel] Merging GSoC projects

[Lucas van Dijk <info return1 net>]

Hi all,

Yeah my project isn't really ready for a merge yet, and unfortunately time is very limited nowadays. I should have more free time in the second semester of this year, so then I'll continue. 

The last part I've worked on is indeed creating some extra configure arguments (without using CFLAGS), so you could call './configure --with-mmcu=atmega168 --with-cpu-freq=8000000'. This is easier to use as a user and easier check if it's already in the configure command string in the Anjuta configure dialog. 

This partly worked. It was a bit strange because in configure.ac the $MMCU variable did contain the right value (the ./configure call arguments), but $CPU_FREQ didn't. $CPU_FREQ was just empty, while it's the same code.
The script can be found here:
https://code.google.com/p/anjuta-avr/source/browse/project-wizard/configure.ac.tpl
(I've moved to google code)

I do want some user friendly widgets in the configure dialog used for setting the MMCU and the CPU freq, that part actually sort of worked, but it was a bit hacky and I had some troubles updating the ./configure string in the dialog. We should think about how to let plugins extend the configure dialog in a nice way.

With kind regards,
Lucas

2011/10/3 Naba Kumar <naba kumar gmail com>

HI Seb,

2011/10/1 Sébastien Granjoux <seb sfo free fr>:

>
> I don't know what the status of Lucas's project neither but I remember that
> it needs some changes in Anjuta and perhaps some additional discussions. The
> last point was about using autotools instead of makefiles, is this working?
>

The project is incomplete as of now. Unfortunately, Lucas is not able
to continue it now because of other studies. He said he would continue
it later next year.

> I remember that I have proposed to create an AnjutaProgram object to store a
> program name with its arguments and its environment. I think that's ok but
> someone, probably me, has to write it. Anyway, it's not necessary just "nice
> to have".
>
> Then, I think the main point is that it needs an improvement in the
> configure dialog allowing to add a custom widget to select the target and
> possibly some additional attributes. That's fine for me but I think Naba
> wasn't completely agree with this.
>
> This is not mandatory as you can always write additional configure argument
> in the existing text entry but I think it is useful to have something more
> user friendly. Is there some changes here?
>
>

AFAIR, it didn't go that far. Current implementation has a project
wizard and configure dialog that patches the command arguments (using
standard widgets). The last thing he was trying was get the configure
options working via autoconf switch in project's configure.ac. I don't
know if he managed to get it working. Then other things like debugger
integration, execution in emulator etc. weren't done because he ran
out of time.

Lucas, perhaps you want to fill in or correct me, but I believe he
sent out a last report summarizing the final state of the project.

Then about merging, this project is supposed to be independent of
anjuta main source, so no merging is needed (except for the changes in
anjuta to make it work together). However, if someone wants to help
develop it further, the source can be found at:
http://gitorious.org/anjuta-avr-environment

Regards,
-Naba

_______________________________________________
anjuta-devel-list mailing list
anjuta-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/anjuta-devel-list