Re: import project & .anjuta project file
- From: Biswapesh Chattopadhyay <biswapesh_chatterjee tcscal co in>
- To: Jeroen Zwartepoorte <jeroen xs4all nl>
- Cc: GNOME Devtools <gnome-devtools gnome org>, JP Rosevear <jpr ximian com>
- Subject: Re: import project & .anjuta project file
- Date: 29 Jan 2003 10:09:53 +0530
> Hi all,
>
> I just committed the attached patches to gnome-build and anjuta2.
>
> The patch to gnome-build adds a "probe" method to the GbfProject
> abstract class. This method returns TRUE when the backend is capable of
> loading the project in the specified directory. In case of the automake
> backend, it checks whether the directory contains a Makefile.am and
> configure.in or configure.ac.
>
> The anjuta2 patch adds an Import Project menuitem for importing existing
> projects into anjuta2. What it does is ask the available backends if
> they can load the project (probe) and then allow the user to choose one.
> It will then create a new .anjuta file (XML) which atm only contains the
> backend with which to load the project. My next step will be to add mime
> type support for .anjuta files, so you can load a project by clicking on
> an .anjuta file in nautilus.
Coolness. BTW, I installed Ajuta2 from scratch (GNOME 2.2 + jhbuild on
RH 7.3, XFree CVS) and used the wizard to generate a new skeleton. But
only the symbol browser tab is visible. Where have the Targets/SOurces
tabs gone and how do I get them back ?
Rgds,
Biswa.
>
> Jeroen
>
> (See attached file: anjuta2.patch)
> (See attached file: gbf.patch)
> (See attached file: InterScan_SafeStamp.txt)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]