rottenwheel/monero
1
0
Fork 0
mirror of https://codeberg.org/anoncontributorxmr/monero.git synced 2024-11-23 18:47:36 -07:00
Code Issues Actions Packages Projects Releases Wiki Activity
8b3b106ad1
monero/tests/core_tests/CMakeLists.txt

93 lines
2.6 KiB
CMake
Raw Normal View History

Update copyright year to 2020 Update copyright year to 2020
2020-05-06 20:36:54 -06:00
# Copyright (c) 2014-2020, The Monero Project
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
#
# 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(core_tests_sources
block_reward.cpp
block_validation.cpp
chain_split_1.cpp
chain_switch_1.cpp
chaingen.cpp
chaingen001.cpp
chaingen_main.cpp
double_spend.cpp
integer_overflow.cpp
add multisig core test and factor multisig building blocks
2017-09-26 16:16:25 -06:00
multisig.cpp
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
ring_signature_1.cpp
transaction_tests.cpp
core_tests: add tests for hard fork behaviors (MRL-0004) We also replace the --fakechain option with an optional structure containing details about configuration for the core/blockchain, for test purposes. This seems more future friendly.
2016-02-08 11:47:56 -07:00
tx_validation.cpp
Adding support for hidden (anonymity) txpool
2019-11-02 14:36:03 -06:00
tx_pool.cpp
Add rct core tests
2016-06-27 11:56:19 -06:00
v2_tests.cpp
Bulletproof aggregated verification and tests Also constrains bulletproofs to simple rct, for simplicity
2018-03-30 13:29:42 -06:00
rct.cpp
device/trezor: debugging features, trezor tests
2018-11-20 06:40:51 -07:00
bulletproofs.cpp
Integrate CLSAGs into monero They are allowed from v12, and MLSAGs are rejected from v13.
2019-06-09 07:02:16 -06:00
rct2.cpp
device/trezor: debugging features, trezor tests
2018-11-20 06:40:51 -07:00
wallet_tools.cpp)
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
set(core_tests_headers
block_reward.h
block_validation.h
chain_split_1.h
chain_switch_1.h
chaingen.h
chaingen_tests_list.h
double_spend.h
double_spend.inl
integer_overflow.h
add multisig core test and factor multisig building blocks
2017-09-26 16:16:25 -06:00
multisig.h
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
ring_signature_1.h
Adding support for hidden (anonymity) txpool
2019-11-02 14:36:03 -06:00
tx_pool.h
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
transaction_tests.h
core_tests: add tests for hard fork behaviors (MRL-0004) We also replace the --fakechain option with an optional structure containing details about configuration for the core/blockchain, for test purposes. This seems more future friendly.
2016-02-08 11:47:56 -07:00
tx_validation.h
Add rct core tests
2016-06-27 11:56:19 -06:00
v2_tests.h
Bulletproof aggregated verification and tests Also constrains bulletproofs to simple rct, for simplicity
2018-03-30 13:29:42 -06:00
rct.h
device/trezor: debugging features, trezor tests
2018-11-20 06:40:51 -07:00
bulletproofs.h
Integrate CLSAGs into monero They are allowed from v12, and MLSAGs are rejected from v13.
2019-06-09 07:02:16 -06:00
rct2.h
device/trezor: debugging features, trezor tests
2018-11-20 06:40:51 -07:00
wallet_tools.h)
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
always use core_tests for consistency, not coretests Other tests use unit_tests, performance_tests, etc. This fixes getting it wrong half the time when typing.
2017-10-19 09:46:17 -06:00
add_executable(core_tests
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
${core_tests_sources}
${core_tests_headers})
always use core_tests for consistency, not coretests Other tests use unit_tests, performance_tests, etc. This fixes getting it wrong half the time when typing.
2017-10-19 09:46:17 -06:00
target_link_libraries(core_tests
cmake: transitive deps and remove deprecated LINK_* Keep the immediate direct deps at the library that depends on them, declare deps as PUBLIC so that targets that link against that library get the library's deps as transitive deps. Break dep cycle between blockchain_db <-> crytonote_core. No code refactoring, just hide cycle from cmake so that it doesn't complain (cycles are allowed only between static libs, not shared libs). This is in preparation for supproting BUILD_SHARED_LIBS cmake built-in option for building internal libs as shared.
2016-09-17 11:59:29 -06:00
PRIVATE
add multisig core test and factor multisig building blocks
2017-09-26 16:16:25 -06:00
multisig
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
cryptonote_core
2014 network limit 1.3 fix log/path/data +utils +toc -doc -drmonero Fixed the windows path, and improved logging and data (for graph) logging, fixed some locks and added more checks. Still there is a locking error, not added by my patches, but present in master version (locking of map/list of peers).
2015-02-24 12:12:56 -07:00
p2p
build: auto update version info without manually deleting version.h
2017-09-13 17:28:23 -06:00
version
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 09:34:23 -07:00
epee
Code modifications to integrate Ledger HW device into monero-wallet-cli. The basic approach it to delegate all sensitive data (master key, secret ephemeral key, key derivation, ....) and related operations to the device. As device has low memory, it does not keep itself the values (except for view/spend keys) but once computed there are encrypted (with AES are equivalent) and return back to monero-wallet-cli. When they need to be manipulated by the device, they are decrypted on receive. Moreover, using the client for storing the value in encrypted form limits the modification in the client code. Those values are transfered from one C-structure to another one as previously. The code modification has been done with the wishes to be open to any other hardware wallet. To achieve that a C++ class hw::Device has been introduced. Two initial implementations are provided: the "default", which remaps all calls to initial Monero code, and the "Ledger", which delegates all calls to Ledger device.
2018-02-20 09:01:27 -07:00
device
device/trezor: debugging features, trezor tests
2018-11-20 06:40:51 -07:00
wallet
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
${CMAKE_THREAD_LIBS_INIT}
${EXTRA_LIBRARIES})
Bulletproof aggregated verification and tests Also constrains bulletproofs to simple rct, for simplicity
2018-03-30 13:29:42 -06:00
enable_stack_trace(core_tests)
always use core_tests for consistency, not coretests Other tests use unit_tests, performance_tests, etc. This fixes getting it wrong half the time when typing.
2017-10-19 09:46:17 -06:00
set_property(TARGET core_tests
cmake: put each test executable in its own directory
2014-10-21 11:01:56 -06:00
PROPERTY
FOLDER "tests")
add_test(
always use core_tests for consistency, not coretests Other tests use unit_tests, performance_tests, etc. This fixes getting it wrong half the time when typing.
2017-10-19 09:46:17 -06:00
NAME core_tests
COMMAND core_tests --generate_and_play_test_data)
Reference in New Issue Copy Permalink