Re: simple project backend

[Timothee Besset <ttimo idsoftware com>]

Ah. Good to see my patch is generating a bit of interest.

Anjuta1 has a similar thing as anjuta2 for the project. It displays a file
tree, and it displays a 'logical view' of the project. That is sources and
headers mostly. This is pushed further in anjuta2's automake backend,
where it displays the targets in a more organized fashion.

I don't use the logical view. The straight file tree has always been
enough as far as I'm concerned. As every else in a simple project backend,
the logical view would have to be manually maintained. I think the default
would be to have a single top level node with the project name as the
generic target.

TTimo

On 07 Feb 2003 03:01:55 -0300
Gustavo Giráldez <gustavo giraldez gmx net> wrote:

> Hi Timothee,
> 
> I like the idea of a simple project backend overall, but I have a
> question: how do you plan to map the project itself to the current model
> gnome-build imposes.
> 
> What I mean is, for the project to be displayed, you need to map the
> actual project to groups, targets and sources of those targets (in the
> auto* case groups are directories, targets are built things or make
> rules, etc.).  Now, since your backend is meant to be as generic as
> possible, how do you plan to do that?  Will this require changes in the
> gnome-build API?  Showing all files in the directories seems the natural
> thing to do IMO, but you still need the targets.
> 
> Implementation of project modification functions is out of the question,
> which is perfectly fine.  But somehow you need to show the project,
> right?  :-)
> 
> Regards,
> Gustavo
> 
> 
> 
> On Sat, 2003-02-01 at 12:23, Timothee Besset wrote:
> > I have finished a first set of patches for basic project backend.
> > 
> > This backend is intended to provide a generic backend for projects which
> > don't use auto* as their build system. It can be alternative build systems
> > (such as cons and scons), or non C/C++ projects (python, java, etc.).
> > 
> > What is in this set of patches:
> > - a backend in gnome-build
> > - a simple project type for anjuta2
> > 
> > Right now there is no file list displayed, and the build command is
> > hardcoded to "make", but uses the g_io_channel piping to report to
> > anjuta2. I am submitting this patch now because further steps on the
> > simple backend will need to be discussed.
> > 
> > I have copied over some elements of the auto* backend to the simple
> > backend, but the clean solution would be to have a few pieces of the code
> > available to all backends:
> > 
> > - running commands/build queue (through g_io_channel)
> > - parsing gcc output to locate errors
> > 
> > For the most up to date info about this patch, see my anjuta2 page:
> > http://ttimo.net/web/anjuta2/
> > 
> > TTimo
> 
> _______________________________________________
> gnome-devtools mailing list
> gnome-devtools gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-devtools
>