Re: Anjuta2 -- problem importing Anjuta project files



On Sun, 2002-10-06 at 10:03, Jeroen Zwartepoorte wrote:
> On Sun, 2002-10-06 at 15:49, John Palmieri wrote:
> > On Sun, 2002-10-06 at 03:43, Jeroen Zwartepoorte wrote:
> > > On Sun, 2002-10-06 at 05:59, John Palmieri wrote:
> > > > Hello,
> > > > 
> > > > I have a wierd problem with projects in Anjuta2.  I want to start
> > > > weaning myself off the fantastik Anjuta platform and start getting
> > > > comfortable with Anjuta2.  At first loading an old Anjuta project works,
> > > > but when I close out of Anjuta2 and then load it back up again I get an
> > > > error dialog stating "Not a proper project!".  Also I can't create
> > > > projects from scratch but I am guessing this functionality is not yet
> > > > implemented.
> > > 
> > > There's a bug in that sometimes when you try to load an automake
> > > project, it will give the above error. You just need to try again until
> > > it loads the project ok.
> > 
> > Ok, do we know where it is failing?  I wouldn't mind going in and trying
> > to fix it if I had an idea of where to look.
> 
> It's failing somewhere in the automake backend in gnome-build. The error
> dialog is shown in anjuta2/plugins/project-manager/project-tool.c:183.
> You should be able to trace that error back all the way to gnome-build.
> The perl script that loads the project is run (as you can see from the
> output in the terminal). The bug is somewhere after that i guess. The
> weird thing is also that it only happens occasionally. I've had it
> happen 3 or four times in a row, but sometimes also the opposite: it
> didn't have for a couple of days.
> 
> This is one of those bugs which has a minor impact and as such can wait
> :)
Hehe, well it is a major bug for me because it consistantly does not
load my project though it does load Anjuta2 and gnome_build most of the
time.  I've tracked down the problem to the "spawn_script" function in
/gnome-build/src/backends/libgbf_am/gbf-am-project.c file.  It seems
like it is not getting the output correctly from the script
(data->output.length==0).  I can run gbf-am-parse -d --get
/home/quinticent/Projects/project1 on the command line and it returns
XML output that looks correct.  I'm going to keep hacking at it but I
don't know how much futher I can get.  Perhaps this will help someone
who is more familiar with the script spawning code and piped input.

--
J5




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