2e5bfc14f2
For external parsing there will be a separate process that handles parse requests sent from MaxScale. From MaxScale's perspective there will just be a specific query classifier plugin that upon startup launches that external process and manages its lifetime. That is, MaxScale proper will be completely oblivious of this arrangement. The skeleton process introduced here does nothing; just sits in a loop sleeping. The skeleton query classifier plugin currently loads the MySQL embedded query classifier and performs parsing using it. That way the external process based query classifier can immediately be used. Next step is to introduce process management into the picture without actually moving the parsing anywhere.
8 lines
322 B
CMake
8 lines
322 B
CMake
add_library(qc_pp SHARED qc_pp.c)
|
|
|
|
target_link_libraries(qc_pp maxscale-common)
|
|
set_target_properties(qc_pp PROPERTIES LINK_FLAGS -Wl,--version-script=${CMAKE_CURRENT_SOURCE_DIR}/qc_pp.map)
|
|
set_target_properties(qc_pp PROPERTIES LINK_FLAGS -Wl,-z,defs)
|
|
|
|
install(TARGETS qc_pp COMPONENT lib DESTINATION ${MAXSCALE_LIBDIR})
|