|
The CEDET Project management system provides a few simple keystrokes for organizing your files, building Makefiles or Automake files, and compiling your sources. If you don't want CEDET to manage your Makefiles, CEDET will still be able to identify some types of projects based on pre-existing build configurations, such as the Emacs sources, the Linux kernel, or any project built using Automake. The entire CEDET Makefile tree was built with CEDET's project management system, so when you download and build the distribution package, you will be using a CEDET project. The image to the right shows a part of the Project management menu.
The project system for CEDET is implemented in a tool called EDE, or "Emacs Development Environment". The EDE tool was started in 1997 and is the backbone of many CEDET features. This section will refer to EDE. The key reason to enable global-ede-mode with your CEDET install is to enable the other tools in the CEDET suite to identify the boundaries of your project. In particular, the smart completion system and the Symref system must be able to find all your sourcecode in order to provide the desired results. Use EDE to create makefilesIf you would like to use EDE to do all the build management of your
sourcecode, and your project is built from C/C++ code, Emacs Lisp
code, and texinfo documentation, then you are in luck. Start with the
command:
and choose either a Makefile or Automake based project. You can then
use
to create makefile targets and start adding source files into your project. Use the project menu to create your makefiles, and build your sources. Use EDE to wrap a known project typeIf you are working on the code to Emacs, Linux, or have a project using hand-written Automake files, then you are in luck. All you need to do is enable EDE's global mode, and that's it. EDE will autodetect these project types, and configure itself to help you use the other features that need the EDE structure. Use EDE to wrap a project with a custom build scriptIf you are working with a custom build system, or a system not yet supported by default by EDE, then you will need to wrap your project in a simple EDE wrapper. For C or C++ projects, there is a custom project you can use called ede-cpp-root. You can configure this project in your .emacs file. A simple example looks like this:
EDE likes to anchor its projects to files on the filesystem, so be
sure to set FILENAME to a real file in your project, such as a
Makefile. The remaining slots are optional, but allow to to
specify project specific include paths, or pre-processor tables.
In this case "spp" stands for the "Semantic PreProcessor",
the tool used to parse C PreProcessor statements.
All the CEDET tools are available from a single distribution file. CEDET is currently driving toward a 1.0 release. Try out a pre-release and send in bug reports on the build process, or anything else to the mailing list. Try out cedet-1.0pre6.tar.gz. After building CEDET, consider adding your results to the prerelease tested configuration page by adding your own platform information. Please Note: If you encounter build problems with a CEDET release, those issues
may have already been fixed in CVS! CEDET has an active community
of users that help identify and fix these issues quickly. You can check the
mailing list archives or just try the
CVS version directly.
|
|   |
|
|
Eric's homepage|
Copyright(C) 1997,98,99,2000,01,02,03,04,05,06,07,08,09 Eric M. Ludlam Verbatim copying and distribution is permitted in any medium, provided this notice is preserved. |