lean2/src/library/tactic/CMakeLists.txt

add_library(tactic goal.cpp proof_builder.cpp cex_builder.cpp
proof_state.cpp tactic.cpp boolean_tactics.cpp apply_tactic.cpp
simplify_tactic.cpp)

target_link_libraries(tactic ${LEAN_LIBS})
refactor(bindings/lua): move Lua bindings to the file associated with them The directory bindings/lua was getting too big and had too many dependencies. Moreover, it was getting too painful to edit/maintain two different places. Now, the bindings for module X are in the directory that defines X. For example, the bindings for util/name.cpp are located at util/name.cpp. The only exception is the kernel. We do not want to inflate the kernel with Lua bindings. The bindings for the kernel classes are located at bindings/kernel_bindings. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-27 03:15:49 +00:00			`add_library(tactic goal.cpp proof_builder.cpp cex_builder.cpp`
feat(library/tactic): add simplify_tactic based on the simplifier Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2014-01-27 02:52:41 +00:00			`proof_state.cpp tactic.cpp boolean_tactics.cpp apply_tactic.cpp`
			`simplify_tactic.cpp)`
refactor(bindings/lua): move Lua bindings to the file associated with them The directory bindings/lua was getting too big and had too many dependencies. Moreover, it was getting too painful to edit/maintain two different places. Now, the bindings for module X are in the directory that defines X. For example, the bindings for util/name.cpp are located at util/name.cpp. The only exception is the kernel. We do not want to inflate the kernel with Lua bindings. The bindings for the kernel classes are located at bindings/kernel_bindings. Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-27 03:15:49 +00:00
feat(library/tactic): add tactic framework APIs Signed-off-by: Leonardo de Moura <leonardo@microsoft.com> 2013-11-21 01:02:41 +00:00			`target_link_libraries(tactic ${LEAN_LIBS})`