Blender V4.3
libmv/logging/logging.h
Go to the documentation of this file.
1// Copyright (c) 2007, 2008, 2009 libmv authors.
2//
3// Permission is hereby granted, free of charge, to any person obtaining a copy
4// of this software and associated documentation files (the "Software"), to
5// deal in the Software without restriction, including without limitation the
6// rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
7// sell copies of the Software, and to permit persons to whom the Software is
8// furnished to do so, subject to the following conditions:
9//
10// The above copyright notice and this permission notice shall be included in
11// all copies or substantial portions of the Software.
12//
13// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
18// FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
19// IN THE SOFTWARE.
20
21#ifndef LIBMV_LOGGING_LOGGING_H
22#define LIBMV_LOGGING_LOGGING_H
23
24#include <glog/logging.h>
25
26// Note on logging severity and verbosity level.
27//
28// Reserve LOG(INFO) for messages which are always to be put to log and don't
29// use the INFO severity for the debugging/troubleshooting type of messages.
30// Some reasoning behind:
31//
32// - Library integration would want to disable "noisy" messages coming from
33// algorithms.
34//
35// - It is not possible to disable INFO severity entirely: there is enough
36// of preparation being done for the message stream. What is even worse
37// is that such stream preparation causes measurable time spent in spin
38// lock, ruining multi-threading.
39
40#define LG VLOG(1)
41
42#endif // LIBMV_LOGGING_LOGGING_H