Next: , Up: Anatomy of a Emodule   [Contents][Index]


2.1 Special Header Files

Every emodule better includes the file emodules-ng.h. This will primarily set up certain vital macros. If you want to stay close to the rest of the SXEmacs binary, for example provide lisp bindings of your stuff or implement functionality depending on whether or not SXEmacs was configured with a certain feature, you should have a thorough glance at sxemacs.h.

Most emodules will probably require some pre-processor conditionals based on constants defined in config.h which is included automatically upon inclusion of sxemacs.h. This file is automatically generated during the configure phase of SXEmacs, its prototype is config.h.in which in turn is autogenerated from various macros in the m4/ directory and configure.ac.

Depending on what your emodule will be doing at last, you will probably need to include other header files as well.