OpMessage enum?OpMessage. Messages
can be added by all modules listed in readme.txt in the
folders modules/, adjunct/ and platforms/. The
messages are read from the file module.messages if present in
the module root.
MSG_NAME message-owner Description text. Depends on: list of features, defines
MSG_ES_RUN jl Runs the ecmascript scheduler. Depends on: FEATURE_ECMASCRIPTThis will cause the following to be added to the
OpMessage enum:
enum OpMessage
{
MSG_NO_MESSAGE,
...
...
#ifdef FEATURE_ECMASCRIPT == YES
,MSG_ES_RUN
#endif // FEATURE_ECMASCRIPT == YES
};
OpMessage enum?
The build-system can be told compile the "current" or "next" mainline
configuration. Each mainline configuration has an associated version
number. If the setup script finds the
file module.messages.version, it parses that
file instead of the module.messages. Thus a message can
be added or changed for only one mainline configuration.
It is recommended to only keep the versiond
file module.messages.version for the "current"
mainline configuration and use the default file for the "next"
mainline configuration. Thus on switching the mainline version
numbers, the versioned file can be removed and only the not-versioned
file remains.
Example: If the "current" mainline version is 2.3 and the "next" mainline version is 2.4, and one module needs to use different dependencis for one message on different mainline configurations, it can use two files:
module.messages.2.3module.messages
So if you want to add or change a message for the "next" mainline
configuration, look for the version number of the "current" mainline
configuration in modules/hardcore/version.ini. If the
file module.messages.current_version exists, you
can edit module.messages.
Otherwise copy module.messages
to module.messages.current_version, add it to the
repository and modify module.messages. Thus the "current"
mainline configuration remains unchanged.
The same applies if you want to add or change a message for the
"current" mainline configuration: look for the version number of the
"current" mainline configuration
in modules/hardcore/version.ini. If the
file module.messages.current_version exists, you
can edit it
Otherwise copy module.messages
to module.messages.current_version, add it to
the repository and modify it. Thus the "next" mainline configuration
remains unchanged.