File: config.el.html

Some auto-detecting projects (such as the 'generic' project type) can be enhanced by also saving a configuration file that is EDE specific. EDE will be able to load that configuration from the save file as a way of augmenting what is normally already detected.

How To Use:

Subclass ede-extra-config(var)/ede-extra-config(fun), and add the features you want to use. Several mixins are available for adding in C++ or Java support. Bring in the pieces you need.

Your project and targets should all have a common baseclass from ede-project-with-config(var)/ede-project-with-config(fun) or ede-target-with-config(var)/ede-target-with-config(fun). When subclassing the project, be sure to override the class allocated slots for the config-class. This will tie your new project to the new configuration type.

You can also override the file name used to save the configuration object in.

If you need to take special action in project-rescan be sure to also call call-next-method to also get the configuration rescanned.

Note on config file safety:

Normally an EDE project that loads a save file should have it's autoload slot :safe-p set to nil. Projects who save data via config.el can mark their project as :safe-p t. The config system will do the queries needed to protect the user. This allows a generic project to become active in cases where no save file exists, nor is needed.

Defined variables (0)

Defined functions (95)

Defined faces (0)