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

36 lines
710 B
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
include_directories(
${PROJECT_SOURCE_DIR}/include
${PROJECT_SOURCE_DIR}/pcbnew
switch back to original sexpr usage of PTREE, add new DSNLEXER constructor, enforce accessors in kicad.exe
2014-07-07 19:49:14 +00:00
${BOOST_INCLUDE}
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
${CMAKE_CURRENT_SOURCE_DIR}
${CMAKE_BINARY_DIR}
)
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
Update tools/property_tree support so it builds again.
2017-02-02 17:24:52 +00:00
../common/exceptions.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/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}
)
IO benchmark program: RICHIO vs std::fstream and wxStream This compares the performance of RICHIO line readers against other implementations, and can be used for profiling and optimisation. Current benchmarks provided: * richio FILE_LINE_READER * Raw std::ifstream (no LINE_READER wrapper), using getline (so no line length limiting) * LINE_READER wrapper around std::istream, with a std::ifstream implementation * Existing richio wxInputStream wrappers (with File and FFile implemntations)
2017-02-15 08:47:41 +00:00
Add CMakeLists.txt build support for tools/utf8_tests.cpp
2017-07-24 14:01:02 +00:00
add_executable( utf8_tests
EXCLUDE_FROM_ALL
utf8_tests.cpp
)
target_link_libraries( utf8_tests
common
${wxWidgets_LIBRARIES}
)