The Linux Tools project is a two-faceted project. Firstly, it develops tools and frameworks for writing tools for Linux developers. Secondly, it provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project will produce both best practices and tools related to packaging. The Linux Tools project delivers tools as Eclipse plugins which are used primarily by Linux developers and packagers. The project also aims to deliver various scripts, techniques, and tarballs which ease the process of packaging Eclipse technology for Linux distributions. First release Latest ChangeLog and specfile editor releases, first release of plugin building and packaging tools (RPM Stubby), resurrected OProfile plugin, initial eclipse.org release of autotools, libhover, valgrind, and systemtap editor plugins. Release candidate build towards 0.2 initial cachegrind support improved OProfile privilege-escalation 0.2 release initial cachegrind support, improved OProfile privilege-escalation, pre- and post-build steps for autotool'd projects, compare support for RPM .spec files, mass BIRT chart interactivity, greatly improved test coverage, many bugfixes 0.3 release wiki-based help documentation, initial integration of SystemTapGUI contribution, integration of SystemTap editor and SystemTapGUI, more robust Valgrind interaction, manual control of OProfile daemon, 3.5 SDK packaging tools (eclipse-build) 0.4 release integration of GProf contribution, 3.5.1 SDK packaging tools (eclipse-build), plugin building scripts (package-build), SDK test running scripts, Systemtap-backed call graph functionality, 0.4.1 bug-fix release Bug fixes for 0.4.0: https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;target_milestone=0.4.1;product=Linux Tools;classification=Technology 0.5 release integration of LTTng contribution, further improvements to ease distro consumption of eclipse-build, integration of GCov contribution, initial release of man page viewer, initial release of SystemTap GUI dashboard 1.0 release SDK packaging tools: 3.5.x eclipse-build, SDK tests, plugin building scripts, testing scripts, scripts for running SDK tests against distro packages; Native development tools: Tracing tools, Systemtap integration, Autotools, libhover, ChangeLog, OProfile, Valgrind, GProf, LTTng For releases <= 0.2, the tools run with Eclipse 3.4.x (some may still require updating from 3.3 in places) and require Java 5.0. Some tools -- notable the autotools and profiling plugins -- require CDT >= 5.0.0 (6.0 for our 0.3 release and greater). For releases >= 0.3, the tools run with Eclipse 3.5.x and related dependencies. The packaging tools not delivered as Eclipse plugins have varying requirements but generally require basic tools such as bash, sh, sed, awk, grep, etc. The tools aim to have all strings externalized so as to facilitate internationalization. At present, no translations are provided. See bug #261255 and bug #261256. The Linux Tools project differs in aims from many Eclipse projects. It enables adopters of Eclipse technology but often through help with consumption and not always through APIs. It also aims to be a place for collaboration among Linux distributions. The project also aims to bring Eclipse technology to Linux developers by providing tools targetted at Linux developers -- specifically those programming in C and C++. Most Linux distributions require all packages included therein to be built directly from source code. This theme encompasses the project goal of assisting distributions in their building and packaging of the Eclipse SDK as well as standardizing practices and any patches needed. It also aims to encourage and aid distributions in their attempts to drive unit test results down to zero. Getting plugins into Linux distributions relates to the project's goal of making it easier to build and package Eclipse plugins for Linux distributions. At present it includes shell scripts and best practice documentation. In the future, we aim to provide Eclipse plugins to help packagers. Many open source projects use GNU-style ChangeLog files to manage their changes. These plugins help writing ChangeLogs and provide an editor for ChangeLog files. Although these plugins are largely mature, we should continue to fix any bugs and increase their robustness. OProfile is a very commonly used Linux profiling tool. The project aims to deliver seamless OProfile-based profiling of CDT projects, integrated into the workbench. We should continue to add features to and improve the robustness of the RPM specfile editor and its related plugins. This set of plugins allows projects that are built using the GNU Autotools (automake, autoconf, etc.) to be developed using the CDT. It relies upon the CDT build mechanisms. This code was submitted in September 2008 and is currently undergoing parallel IP review. Goals include managing new file addition to targets, small wizards to ease creation of various build targets, and tools to export an "autotooled" build. This set of plugins provides a framework to provide editor hover help for various popular libraries a developer may need for C/C++ development. A new library can add hover help for its interfaces simply by creating a special xml file and using the libhover extension. Ideally, library maintainers would create the information from existing doc files and add it to their packages. Goals include providing hover help for many popular C libraries, allowing selection of hover help per project, and promoting library providers to create these plugins as part of their own build process. This plugin offers an editor for Systemtap scripts. Syntax highlighting and completion are initial items that will be delivered. Also see Phil Muldoon's blog entry introducing the project. Valgrind is a set of tools very commonly used to diagnose memory-related issues among other things. We intend to make using valgrind tools from within Eclipse very simple. Integrating the output of the valgrind tools into the IDE will be a focus as will be simplicity. Tracing frameworks such as SystemTap and LTTng enable users to solve complex problems through data analysis. We aim to provide a framework for working with tracing toolkits and provide an exemplary implementation for LTTng.