Log a message.
General messages¶
Record the specified message text in the log. If more than one messagestring is given, they are concatenated into a single message with noseparator between the strings.
The optional <mode> keyword determines the type of message, whichinfluences the way the message is handled:
7 days for easily accessible message trace, 90 days for “Historical Search” – where results can only be viewed in a downloadable CSV file. Availability: All data about messages is available as soon as they are sent or received. Messages less than 4 hours old might not be available. Delay: All searches start immediately.
- =How To Install Packet Tracer On macOS Sierra=1.- Packet Tracer Wine Bottler http://winebottler.
- Trace any email address online. Just Paste the email message source and locate the original sender IP, real location, latitudes, and longitudes with the best email header analyzer tool in the market.
FATAL_ERRORCMake Error, stop processing and generation.
SEND_ERRORCMake Error, continue processing, but skip generation.
WARNINGCMake Warning, continue processing.
AUTHOR_WARNING
CMake Warning (dev), continue processing.
DEPRECATIONCMake Deprecation Error or Warning if variableCMAKE_ERROR_DEPRECATED or CMAKE_WARN_DEPRECATEDis enabled, respectively, else no message.
NOTICEImportant message printed to stderr to attract user's attention.
STATUSThe main interesting messages that project users might be interested in.Ideally these should be concise, no more than a single line, but stillinformative.
VERBOSEDetailed informational messages intended for project users. These messagesshould provide additional details that won't be of interest in most cases,but which may be useful to those building the project when they want deeperinsight into what's happening.
DEBUGDetailed informational messages intended for developers working on theproject itself as opposed to users who just want to build it. These messageswill not typically be of interest to other users building the project andwill often be closely related to internal implementation details.
TRACEFine-grained messages with very low-level implementation details. Messagesusing this log level would normally only be temporary and would expect to beremoved before releasing the project, packaging up the files, etc.
New in version 3.15: Added the NOTICE, VERBOSE, DEBUG, and TRACE levels.
The CMake command-line tool displays STATUS to TRACE messages on stdoutwith the message preceded by two hyphens and a space. All other message typesare sent to stderr and are not prefixed with hyphens. TheCMakeGUI displays all messages in its log area.The cursesinterface shows STATUS to TRACEmessages one at a time on a status line and other messages in aninteractive pop-up box. The --log-level command-line option to each ofthese tools can be used to control which messages will be shown.
New in version 3.17: To make a log level persist between CMake runs, theCMAKE_MESSAGE_LOG_LEVEL variable can be set instead.Note that the command line option takes precedence over the cache variable.
New in version 3.16: Messages of log levels NOTICE and below will have each line precededby the content of the CMAKE_MESSAGE_INDENT variable (converted toa single string by concatenating its list items). For STATUS to TRACEmessages, this indenting content will be inserted after the hyphens.
New in version 3.17: Messages of log levels NOTICE and below can also have each line precededwith context of the form [some.context.example]. The content between thesquare brackets is obtained by converting the CMAKE_MESSAGE_CONTEXTlist variable to a dot-separated string. The message context will alwaysappear before any indenting content but after any automatically added leadinghyphens. By default, message context is not shown, it has to be explicitlyenabled by giving the cmake--log-contextcommand-line option or by setting the CMAKE_MESSAGE_CONTEXT_SHOWvariable to true. See the CMAKE_MESSAGE_CONTEXT documentation forusage examples.
CMake Warning and Error message text displays using a simple markuplanguage. Non-indented text is formatted in line-wrapped paragraphsdelimited by newlines. Indented text is considered pre-formatted.
Reporting checks¶
A common pattern in CMake output is a message indicating the start of somesort of check, followed by another message reporting the result of that check.For example:
This can be more robustly and conveniently expressed using the CHECK_...keyword form of the message() command:
where <checkState> must be one of the following:
CHECK_STARTRecord a concise message about the check about to be performed.
CHECK_PASSRecord a successful result for a check.
CHECK_FAILRecord an unsuccessful result for a check.
Message Tracer Mac Library Application
When recording a check result, the command repeats the message from the mostrecently started check for which no result has yet been reported, then someseparator characters and then the message text provided after theCHECK_PASS or CHECK_FAIL keyword. Check messages are always reportedat STATUS log level.
Checks may be nested and every CHECK_START should have exactly onematching CHECK_PASS or CHECK_FAIL.The CMAKE_MESSAGE_INDENT variable can also be used to addindenting to nested checks if desired. For example:
Message Tracer Mac Library Software
Message Tracer Mac
Output from the above would appear something like the following: