2016-02-20 16:04:56 +00:00
|
|
|
# Copyright (c) 2014-2016, The Monero Project
|
|
|
|
|
#
|
|
|
|
|
# All rights reserved.
|
|
|
|
|
#
|
|
|
|
|
# Redistribution and use in source and binary forms, with or without modification, are
|
|
|
|
|
# permitted provided that the following conditions are met:
|
|
|
|
|
#
|
|
|
|
|
# 1. Redistributions of source code must retain the above copyright notice, this list of
|
|
|
|
|
# conditions and the following disclaimer.
|
|
|
|
|
#
|
|
|
|
|
# 2. Redistributions in binary form must reproduce the above copyright notice, this list
|
|
|
|
|
# of conditions and the following disclaimer in the documentation and/or other
|
|
|
|
|
# materials provided with the distribution.
|
|
|
|
|
#
|
|
|
|
|
# 3. Neither the name of the copyright holder nor the names of its contributors may be
|
|
|
|
|
# used to endorse or promote products derived from this software without specific
|
|
|
|
|
# prior written permission.
|
|
|
|
|
#
|
|
|
|
|
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
|
|
|
|
|
# EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
|
|
|
|
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
|
|
|
|
|
# THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
|
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
|
|
|
|
|
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
|
|
|
|
|
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
|
|
|
|
|
# STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
|
|
|
|
|
# THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
|
|
|
|
|
|
set(libwallet_api_tests_sources
|
|
|
|
|
main.cpp
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
set(libwallet_api_tests_headers
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
add_executable(libwallet_api_tests
|
|
|
|
|
${libwallet_api_tests_sources}
|
|
|
|
|
${libwallet_api_tests_headers})
|
|
|
|
|
|
|
|
|
|
target_link_libraries(libwallet_api_tests
|
2016-09-17 17:59:29 +00:00
|
|
|
PRIVATE
|
2016-02-20 16:04:56 +00:00
|
|
|
wallet
|
Change logging to easylogging++
This replaces the epee and data_loggers logging systems with
a single one, and also adds filename:line and explicit severity
levels. Categories may be defined, and logging severity set
by category (or set of categories). epee style 0-4 log level
maps to a sensible severity configuration. Log files now also
rotate when reaching 100 MB.
To select which logs to output, use the MONERO_LOGS environment
variable, with a comma separated list of categories (globs are
supported), with their requested severity level after a colon.
If a log matches more than one such setting, the last one in
the configuration string applies. A few examples:
This one is (mostly) silent, only outputting fatal errors:
MONERO_LOGS=*:FATAL
This one is very verbose:
MONERO_LOGS=*:TRACE
This one is totally silent (logwise):
MONERO_LOGS=""
This one outputs all errors and warnings, except for the
"verify" category, which prints just fatal errors (the verify
category is used for logs about incoming transactions and
blocks, and it is expected that some/many will fail to verify,
hence we don't want the spam):
MONERO_LOGS=*:WARNING,verify:FATAL
Log levels are, in decreasing order of priority:
FATAL, ERROR, WARNING, INFO, DEBUG, TRACE
Subcategories may be added using prefixes and globs. This
example will output net.p2p logs at the TRACE level, but all
other net* logs only at INFO:
MONERO_LOGS=*:ERROR,net*:INFO,net.p2p:TRACE
Logs which are intended for the user (which Monero was using
a lot through epee, but really isn't a nice way to go things)
should use the "global" category. There are a few helper macros
for using this category, eg: MGINFO("this shows up by default")
or MGINFO_RED("this is red"), to try to keep a similar look
and feel for now.
Existing epee log macros still exist, and map to the new log
levels, but since they're used as a "user facing" UI element
as much as a logging system, they often don't map well to log
severities (ie, a log level 0 log may be an error, or may be
something we want the user to see, such as an important info).
In those cases, I tried to use the new macros. In other cases,
I left the existing macros in. When modifying logs, it is
probably best to switch to the new macros with explicit levels.
The --log-level options and set_log commands now also accept
category settings, in addition to the epee style log levels.
2017-01-01 16:34:23 +00:00
|
|
|
epee
|
2016-09-17 17:59:29 +00:00
|
|
|
${Boost_SERIALIZATION_LIBRARY}
|
|
|
|
|
${Boost_FILESYSTEM_LIBRARY}
|
|
|
|
|
${Boost_SYSTEM_LIBRARY}
|
2016-08-29 17:56:34 +00:00
|
|
|
${GTEST_LIBRARIES}
|
2016-09-17 17:59:29 +00:00
|
|
|
${CMAKE_THREAD_LIBS_INIT}
|
2016-02-20 16:04:56 +00:00
|
|
|
${EXTRA_LIBRARIES})
|
|
|
|
|
|
|
|
|
|
set_property(TARGET libwallet_api_tests
|
|
|
|
|
PROPERTY
|
|
|
|
|
FOLDER "tests")
|
|
|
|
|
|
|
|
|
|
if (NOT MSVC)
|
|
|
|
|
set_property(TARGET libwallet_api_tests
|
|
|
|
|
APPEND_STRING
|
|
|
|
|
PROPERTY
|
|
|
|
|
COMPILE_FLAGS " -Wno-undef -Wno-sign-compare")
|
|
|
|
|
endif ()
|
|
|
|
|
|
|
|
|
|
add_test(
|
|
|
|
|
NAME libwallet_api_tests
|
|
|
|
|
COMMAND libwallet_api_tests)
|
