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

79 lines
1.8 KiB
CMake
Raw Normal View History

add tools directory, move container_test.cpp there on standby
2012-01-23 15:25:46 +00:00
Add tools/parser_gen.cpp which is the beginnings of an s-expression parser generation tool. For now, it is just an s-expression beautifier using our "non-specctra mode" version of s-expressions.
2012-04-30 02:57:48 +00:00
if( 0 )
add tools directory, move container_test.cpp there on standby
2012-01-23 15:25:46 +00:00
Add tools/parser_gen.cpp which is the beginnings of an s-expression parser generation tool. For now, it is just an s-expression beautifier using our "non-specctra mode" version of s-expressions.
2012-04-30 02:57:48 +00:00
project(kicad-tools)
cmake_minimum_required( VERSION 2.8 FATAL_ERROR )
set( PROJECT_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/../ )
# message( "PROJECT_SOURCE_DIR=${PROJECT_SOURCE_DIR}" )
# Path to local CMake modules.
set( CMAKE_MODULE_PATH ${PROJECT_SOURCE_DIR}/CMakeModules )
include( CheckFindPackageResult )
##########################
# Find wxWidgets library #
##########################
# Here you can define what libraries of wxWidgets you need for your
# application. You can figure out what libraries you need here;
# http://www.wxwidgets.org/manuals/2.8/wx_librarieslist.html
# On Apple only wxwidgets 2.9 or higher doesn't need to find aui part of base
if(APPLE)
find_package(wxWidgets COMPONENTS gl adv html core net base xml QUIET)
else(APPLE)
find_package(wxWidgets COMPONENTS gl aui adv html core net base xml QUIET)
endif(APPLE)
check_find_package_result(wxWidgets_FOUND "wxWidgets")
# Include wxWidgets macros.
include(${wxWidgets_USE_FILE})
# make config.h
include( PerformFeatureChecks )
perform_feature_checks()
endif()
include_directories(
${PROJECT_SOURCE_DIR}/include
${PROJECT_SOURCE_DIR}/pcbnew
${CMAKE_CURRENT_SOURCE_DIR}
${CMAKE_BINARY_DIR}
)
add_executable( container_test
EXCLUDE_FROM_ALL
container_test.cpp
)
target_link_libraries( container_test
common
polygon
bitmaps
${wxWidgets_LIBRARIES}
)
legacy_plugin was not round tripping nanometers, add test program to verify new conversion strategy
2012-06-23 23:21:03 +00:00
add_executable( test-nm-biu-to-ascii-mm-round-tripping
EXCLUDE_FROM_ALL
test-nm-biu-to-ascii-mm-round-tripping.cpp
)
Add tools/parser_gen.cpp which is the beginnings of an s-expression parser generation tool. For now, it is just an s-expression beautifier using our "non-specctra mode" version of s-expressions.
2012-04-30 02:57:48 +00:00
Implement "KiCad s-epression" support for boost::property_tree's ptree, the 8 bit string version of property_tree. The ram resident structure of the ptree is mostly compatible with one created using the xml_parser from boost::property_tree, with slight differences in the way atoms are stored. The result is you can use Format() to convert from xml to s-expression, but not the other way around. You can write a simple s-expression beautifier in just a few lines of code. The main value however is the s-expression parser, i.e. Scan(), which is an alternative to crafting a custom recursive descent parser for a particular grammar. The tipping point depends on whether you want to read only a small portion of a much larger document. If so, then using the ptree will likely be a "faster to code" route. Documentation on how to navigate a ptree can be found on the boost website and there are a number of examples in the pcbnew/eagle_plugin.cpp file in this project. Powerful path navigation support makes it easy to extract a subset of a ptree.
2013-04-08 21:04:45 +00:00
add_executable( property_tree
Add tools/parser_gen.cpp which is the beginnings of an s-expression parser generation tool. For now, it is just an s-expression beautifier using our "non-specctra mode" version of s-expressions.
2012-04-30 02:57:48 +00:00
EXCLUDE_FROM_ALL
Implement "KiCad s-epression" support for boost::property_tree's ptree, the 8 bit string version of property_tree. The ram resident structure of the ptree is mostly compatible with one created using the xml_parser from boost::property_tree, with slight differences in the way atoms are stored. The result is you can use Format() to convert from xml to s-expression, but not the other way around. You can write a simple s-expression beautifier in just a few lines of code. The main value however is the s-expression parser, i.e. Scan(), which is an alternative to crafting a custom recursive descent parser for a particular grammar. The tipping point depends on whether you want to read only a small portion of a much larger document. If so, then using the ptree will likely be a "faster to code" route. Documentation on how to navigate a ptree can be found on the boost website and there are a number of examples in the pcbnew/eagle_plugin.cpp file in this project. Powerful path navigation support makes it easy to extract a subset of a ptree.
2013-04-08 21:04:45 +00:00
property_tree.cpp
Add tools/parser_gen.cpp which is the beginnings of an s-expression parser generation tool. For now, it is just an s-expression beautifier using our "non-specctra mode" version of s-expressions.
2012-04-30 02:57:48 +00:00
../common/richio.cpp
../common/dsnlexer.cpp
Implement "KiCad s-epression" support for boost::property_tree's ptree, the 8 bit string version of property_tree. The ram resident structure of the ptree is mostly compatible with one created using the xml_parser from boost::property_tree, with slight differences in the way atoms are stored. The result is you can use Format() to convert from xml to s-expression, but not the other way around. You can write a simple s-expression beautifier in just a few lines of code. The main value however is the s-expression parser, i.e. Scan(), which is an alternative to crafting a custom recursive descent parser for a particular grammar. The tipping point depends on whether you want to read only a small portion of a much larger document. If so, then using the ptree will likely be a "faster to code" route. Documentation on how to navigate a ptree can be found on the boost website and there are a number of examples in the pcbnew/eagle_plugin.cpp file in this project. Powerful path navigation support makes it easy to extract a subset of a ptree.
2013-04-08 21:04:45 +00:00
../common/ptree.cpp
Add tools/parser_gen.cpp which is the beginnings of an s-expression parser generation tool. For now, it is just an s-expression beautifier using our "non-specctra mode" version of s-expressions.
2012-04-30 02:57:48 +00:00
)
Implement "KiCad s-epression" support for boost::property_tree's ptree, the 8 bit string version of property_tree. The ram resident structure of the ptree is mostly compatible with one created using the xml_parser from boost::property_tree, with slight differences in the way atoms are stored. The result is you can use Format() to convert from xml to s-expression, but not the other way around. You can write a simple s-expression beautifier in just a few lines of code. The main value however is the s-expression parser, i.e. Scan(), which is an alternative to crafting a custom recursive descent parser for a particular grammar. The tipping point depends on whether you want to read only a small portion of a much larger document. If so, then using the ptree will likely be a "faster to code" route. Documentation on how to navigate a ptree can be found on the boost website and there are a number of examples in the pcbnew/eagle_plugin.cpp file in this project. Powerful path navigation support makes it easy to extract a subset of a ptree.
2013-04-08 21:04:45 +00:00
target_link_libraries( property_tree
Add tools/parser_gen.cpp which is the beginnings of an s-expression parser generation tool. For now, it is just an s-expression beautifier using our "non-specctra mode" version of s-expressions.
2012-04-30 02:57:48 +00:00
${wxWidgets_LIBRARIES}
)
add tools directory, move container_test.cpp there on standby
2012-01-23 15:25:46 +00:00