"A service to open source is a service to mankind." 

Are you a library or project maintainer?

Then you are looking to provide users of your library or project to use Anjuta for development. To do this Anjuta provides several means to make it easy.

You can start by creating a template for your library. Follow this simple tutorial to create project templates (no programming needed). You can either distribute the templates yourself or you can submit it to Anjuta bugzilla for inclusion in our next release.

Then if you need more advanced stuffs to use your project, you can create plugins to do them. Follow this nice tutorial to create anjuta plugins. Or you can pick up one of existing plugins and start adating it for your project. Plugins have to be distribute separately since they quite specific to your project. You can see some good examples of how it is done with Poky SDK plugin, Maemo plugin, Moblin plugin etc.

We are always listening if you have anything needed in Anjuta for plugins to work. So, feel free to ask for it in our mailing list.

Are you looking to contribute to Anjuta?

Anjuta is maintained in GNOME git server. Git is a very powerfull distributed version control system. To learn more about git and how you can help anjuta development check the GNOME git wiki.

Make sure you have all dependencies of Anjuta installed and ready. Now, grab the anjuta and gdl modules from the repository:

$ git clone git://git.gnome.org/anjuta
$ git clone git://git.gnome.org/gdl

That only gives read access to the repository. If you have an account for git.gnome.org and want write access (you must have been granted write access to the anjuta module as an Anjuta developer), you instead need to check out the source with:

$ git clone ssh://username@git.gnome.org/git/anjuta
$ git clone ssh://username@git.gnome.org/git/gdl

Now you will want to build and install. Run:

$ ./autogen.sh

If you want to enable Anjuta API documentation generation, you can pass --enable-gtk-doc to the above autogen.sh script. Then continue just like you would work with a tarball package:

$ ./configure
$ make
$ su [password]
# make install

At the end of configure stage, you will see which plugins are being built and which aren't. If you see some plugins not built, it's because you are missing some key dependencies to make it build.

After you have checked the code out, you can use:

$ git pull --rebase (in the anjuta top level directory)

to update your personal copy of Anjuta to the latest version from the Git repository and rebuild.

If you want to submit patches or commit to anjuta repository, see this nice and simple git tutorial for further instructions

History

Anjuta project was started in 27th Dec 1997. To learn more about its history visit the first archived anjuta website