haskal
/
kicad
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
kicad/qa/pcbnew_utils/CMakeLists.txt

93 lines
2.9 KiB
CMake
Raw Normal View History

DRC: Break out courtyard overlap function Introduce the concept of a DRC_PROVIDER which allows to separate the various DRC functions to their own areas. This allows, amongst other things, a slimmer core DRC class, and allows DRC functions to be separately testable. The courtyard DRCs (overlap, missing and malformed) are the first victims, so instrumentation can be added to this function. Add some unit tests on this DRC function, as well a few re-usable PCB-based utility functions in a library (qa_pcbnew_utils) that could be shared between unit tests and other utilities.
2019-01-11 22:03:45 +00:00
# This program source code file is part of KiCad, a free EDA CAD application.
#
# Copyright (C) 2019 KiCad Developers, see CHANGELOG.TXT for contributors.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, you may find one here:
# http://www.gnu.org/licenses/old-licenses/gpl-2.0.html
# or you may search the http://www.gnu.org website for the version 2 license,
# or you may write to the Free Software Foundation, Inc.,
# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
# Pcbnew-related auxiliary functions that are useful for QA purposes
Fix source comment / documentation typos
2021-06-09 19:32:58 +00:00
# (both unit tests and utility programs)
DRC: Break out courtyard overlap function Introduce the concept of a DRC_PROVIDER which allows to separate the various DRC functions to their own areas. This allows, amongst other things, a slimmer core DRC class, and allows DRC functions to be separately testable. The courtyard DRCs (overlap, missing and malformed) are the first victims, so instrumentation can be added to this function. Add some unit tests on this DRC function, as well a few re-usable PCB-based utility functions in a library (qa_pcbnew_utils) that could be shared between unit tests and other utilities.
2019-01-11 22:03:45 +00:00
# This is a massive hack in the CMake as I have no idea how to get this to
# link against pcbnew/pcbcommon/etc and still allow a dependency to also link
# THis should really be an add_library() and all the variables instead set using
# target_*() functions.
set( QA_PCBNEW_UTILS_SRCS
${CMAKE_CURRENT_SOURCE_DIR}/board_construction_utils.cpp
${CMAKE_CURRENT_SOURCE_DIR}/board_file_utils.cpp
qa: move unittests to the separate directory
2022-03-18 20:05:15 +00:00
${CMAKE_CURRENT_SOURCE_DIR}/board_test_utils.cpp
DRC: Break out courtyard overlap function Introduce the concept of a DRC_PROVIDER which allows to separate the various DRC functions to their own areas. This allows, amongst other things, a slimmer core DRC class, and allows DRC functions to be separately testable. The courtyard DRCs (overlap, missing and malformed) are the first victims, so instrumentation can be added to this function. Add some unit tests on this DRC function, as well a few re-usable PCB-based utility functions in a library (qa_pcbnew_utils) that could be shared between unit tests and other utilities.
2019-01-11 22:03:45 +00:00
)
add_library( qa_pcbnew_utils STATIC ${QA_PCBNEW_UTILS_SRCS} )
target_include_directories( qa_pcbnew_utils PUBLIC BEFORE ${INC_BEFORE} )
target_include_directories( qa_pcbnew_utils PUBLIC
include
# Paths for pcbnew lib usage (should really be in pcbnew/common
# target_include_directories and made PUBLIC)
${CMAKE_SOURCE_DIR}
${CMAKE_SOURCE_DIR}/include
${CMAKE_SOURCE_DIR}/pcbnew
${CMAKE_SOURCE_DIR}/common
${CMAKE_SOURCE_DIR}/pcbnew/router
${CMAKE_SOURCE_DIR}/pcbnew/tools
${CMAKE_SOURCE_DIR}/pcbnew/dialogs
${INC_AFTER}
)
Add build dependency on pcbcommon in qa test The qa_pcbnew_util needs the pcb_lexer header that is generated as part of pcbcommon, so it must be built after pcbcommon.
2020-03-01 17:03:12 +00:00
add_dependencies( qa_pcbnew_utils
pcbcommon
)
QA: Centralise BOARD reading functions in pcbnew_utils Several pcbnew_tools utilities read a file from the command line. Instead of replicating this code, centralise the code in qa_pcbnew_utils, which allows simpler reuse. THe utilities are: * polygon_triangulation * polygon_generator * drc_tool pcb_parser keeps its own function, as that is the focus of the tool, and its likely to have its own instrumention. This also adds the ability to read from stdin for the above tools, which means fuzz testers could theoretically work with them, and it also can make life easier if you can pipe a board to the executable directly.
2019-01-24 14:56:55 +00:00
target_link_libraries( qa_pcbnew_utils PUBLIC
qa_utils
)
DRC: Break out courtyard overlap function Introduce the concept of a DRC_PROVIDER which allows to separate the various DRC functions to their own areas. This allows, amongst other things, a slimmer core DRC class, and allows DRC functions to be separately testable. The courtyard DRCs (overlap, missing and malformed) are the first victims, so instrumentation can be added to this function. Add some unit tests on this DRC function, as well a few re-usable PCB-based utility functions in a library (qa_pcbnew_utils) that could be shared between unit tests and other utilities.
2019-01-11 22:03:45 +00:00
# 3d-viewer
# connectivity
# pcbcommon
# pnsrouter
# common
# pcbcommon
# gal
# qa_utils
# lib_dxf
# idf3
# unit_test_utils
Altium: Refactor and add initial structure for schematic importer altium: move pcbnew/altium2kicadpcb_plugin -> pcbnew/plugins/altium See: https://gitlab.com/kicad/code/kicad/-/issues/4412
2020-08-23 19:01:08 +00:00
# ${PCBNEW_IO_LIBRARIES}
DRC: Break out courtyard overlap function Introduce the concept of a DRC_PROVIDER which allows to separate the various DRC functions to their own areas. This allows, amongst other things, a slimmer core DRC class, and allows DRC functions to be separately testable. The courtyard DRCs (overlap, missing and malformed) are the first victims, so instrumentation can be added to this function. Add some unit tests on this DRC function, as well a few re-usable PCB-based utility functions in a library (qa_pcbnew_utils) that could be shared between unit tests and other utilities.
2019-01-11 22:03:45 +00:00
# ${wxWidgets_LIBRARIES}
# ${GDI_PLUS_LIBRARIES}
# ${PYTHON_LIBRARIES}
# ${Boost_LIBRARIES} # must follow GITHUB
# ${PCBNEW_EXTRA_LIBS} # -lrt must follow Boost
#)
# # we need to pretend to be something to appease the units code
target_compile_definitions( qa_pcbnew_utils
PUBLIC PCBNEW
Add build dependency on pcbcommon in qa test The qa_pcbnew_util needs the pcb_lexer header that is generated as part of pcbcommon, so it must be built after pcbcommon.
2020-03-01 17:03:12 +00:00
)
Add zone filler tests. One test has pads of a bunch of different shapes and provokes some errors to make sure they're caught. The others are all past issues with the zone filler to make sure we don't suffer any regressions. (They should all just pass with no DRC errors.)
2021-07-30 16:08:12 +00:00
# Pass in the default data location
set_source_files_properties( board_file_utils.cpp PROPERTIES
qa: move pcbnew data to appropriate directory
2022-03-18 21:30:17 +00:00
COMPILE_DEFINITIONS "QA_PCBNEW_DATA_LOCATION=(\"${CMAKE_SOURCE_DIR}/qa/data/pcbnew\")"
Add zone filler tests. One test has pads of a bunch of different shapes and provokes some errors to make sure they're caught. The others are all past issues with the zone filler to make sure we don't suffer any regressions. (They should all just pass with no DRC errors.)
2021-07-30 16:08:12 +00:00
)