Anjuta

Anjuta
http://www.anjuta.org · CC BY-SA 3.0 · source
Name	Anjuta
Developer	GNOME Project
Released	2001
Programming language	C, C++
Operating system	Unix-like
Genre	Integrated development environment
License	GPL

Contents

History
Features
Architecture and Components
Development and Community
Reception and Usage
See also

Anjuta Anjuta is an integrated development environment developed for the GNOME desktop environment, designed to support software development for Linux, BSD, Solaris and other Unix-like platforms. It provided project management, application wizards, interactive debugger integration, and source code editing tailored to GNOME technologies, GTK, Glib and GNOME Platform libraries. Anjuta served as part of the GNOME ecosystem alongside tools such as Glade, Devhelp, and GDB, and influenced workflows around GNOME Builder and other IDEs.

History

Originally created in the early 2000s, Anjuta emerged during a period of rapid growth in the GNOME and free software communities, contemporaneous with projects like KDE, Xfce, and LXDE. It was developed amid contributions from Red Hat, Novell, Sun Microsystems developers, and independent contributors who had ties to projects such as Fedora, Ubuntu, Debian, Gentoo, OpenBSD and FreeBSD. Over time Anjuta integrated with build systems and tooling including Autotools, CMake, GNU Make, and pkg-config, aligning with standards set by freedesktop.org and the Linux Standard Base. The project interacted with the GNOME release cadence, GNOME Shell introductions, and the GNOME Mobile initiatives that involved organizations like Nokia and Intel. As GNOME evolved through versions such as GNOME 2, GNOME 3 and subsequent libraries like GTK+ and GTK4, Anjuta’s role shifted while alternatives including Eclipse, NetBeans, Visual Studio Code, and JetBrains IDEs gained prominence. The project’s activity waned as GNOME Builder and other editors expanded feature sets, and stewardship shifted between individual maintainers, community members from GNOME Foundation circles, and contributors from distribution communities like Arch Linux and OpenSUSE.

Features

Anjuta offered a set of features oriented to C and C++ developers working with GNOME technologies and common Unix toolchains. Integrated features included a source editor with syntax highlighting, code completion and symbol browsing comparable to offerings from Eclipse, KDevelop and Code::Blocks; project management supporting templates for GNOME Applications and GTK programs as seen in Glade-driven UI efforts; and debugging integration using GDB front-ends similar to DDD and Nemiver. It supported version control systems such as Git, Subversion and CVS used by projects like the Linux kernel, GNOME, KDE, LibreOffice and Apache, and interfaced with tools like Valgrind for memory analysis and the GNU Compiler Collection, Clang and LLVM for compilation. Internationalization support aligned with gettext workflows used by Fedora, Debian, Ubuntu and open source translators coordinated via Transifex and GNOME Translation Project. Plugin architecture allowed extensions akin to plugin ecosystems in Eclipse, NetBeans and Visual Studio Code.

Architecture and Components

Anjuta’s architecture combined UI components built with GTK and Glib, libraries and modules for parsing and symbol indexing, and backend integrations with build and debug tools. Core components included a project manager supporting Autotools and CMake generated projects, a source editor leveraging GtkSourceView similar to tools such as Gedit and Pluma, and a debugger frontend communicating with GDB like Nemiver and DDD. Integration points with Devhelp provided API documentation browsing for GTK, Glib, GObject, Libxml2 and Cairo libraries, while Glade was used for designing interfaces alongside libraries from Pango and ATK for accessibility features maintained by GNOME Accessibility efforts. The plugin system allowed third-party modules to extend support for languages and frameworks such as Python, Vala, JavaScript (GJS), Mono, Qt and SDL, comparable to language support plugins for Eclipse and JetBrains IntelliJ Platform.

Development and Community

Development occurred within the GNOME infrastructure, using platforms such as git, GNOME GitLab, Bugzilla historically, and later issue trackers and mailing lists tied to the GNOME Foundation. Contributors included freelancers, employees of corporations like Red Hat, Canonical, Intel, Nokia and SUSE, and volunteers active in communities around Fedora, Ubuntu, Debian, Arch Linux and OpenSUSE. The community coordinated with related projects including GNOME Builder, Glade, Devhelp, GTK, GObject Introspection, Flatpak packaging efforts, and CI systems used by GitLab CI, Jenkins and Travis CI. Outreach and events took place at conferences and summits such as GUADEC, FOSDEM, SCALE, Linux Plumbers Conference, LinuxCon and Open Source Summit, with collaborations involving organizations like the Free Software Foundation, Open Source Initiative and Software Freedom Conservancy.

Reception and Usage

Anjuta was well-regarded among GNOME application developers, GTK and Glib programmers, and contributors to projects such as Evolution, GNOME Shell extensions and GNOME Core Apps for its integration with GNOME technologies. Reviews and comparisons referenced alternatives like Eclipse, NetBeans, KDevelop, Geany, Kate, Emacs and Vim, and later editors such as Sublime Text and Visual Studio Code. While distributions like Fedora, Ubuntu and Debian packaged Anjuta, many developers migrated to GNOME Builder, IDEs from JetBrains, or editor-centric workflows using Language Server Protocol implementations from Microsoft, Red Hat and the Eclipse Foundation. Academic courses and workshops on GTK programming, GObject, and open source application development historically included Anjuta among recommended tools alongside documentation from projects like LibreOffice, Xfce, and LXDE.

History

Features

Architecture and Components

Development and Community

Reception and Usage

See also