wbtiger
/
foundationdb
mirror of https://github.com/apple/foundationdb.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
foundationdb/fdbcli/CMakeLists.txt

15 lines
348 B
CMake
Raw Normal View History

CMake compiles all binaries except for bindings
2018-05-04 07:06:30 +08:00
set(FDBCLI_SRCS
fdbcli.actor.cpp
FlowLineNoise.actor.cpp
FlowLineNoise.h
linenoise/linenoise.h)
fdbservice and fdbrpc now compiling
2019-02-07 11:27:38 +08:00
if(NOT WIN32)
Fix typo that breaks linux build
2019-02-06 08:47:39 +08:00
list(APPEND FDBCLI_SRCS linenoise/linenoise.c)
fdbservice and fdbrpc now compiling
2019-02-07 11:27:38 +08:00
endif()
simplify actorcompiler and target to compile coveragetool
2019-02-09 08:51:13 +08:00
add_flow_target(EXECUTABLE NAME fdbcli SRCS ${FDBCLI_SRCS})
CMake compiles all binaries except for bindings
2018-05-04 07:06:30 +08:00
target_link_libraries(fdbcli PRIVATE fdbclient)
Some more improvements to the build and preparations for packaging
2018-05-06 00:43:50 +08:00
First implementaion of more user-friendly cpack Up unto here this code is only very rudiemantery tested. This is a firest attempt of making cpack more user-friendly. The basic idea is to generate a component for package type so that we can have different paths depending on whether we build an RPM, a DEB, a TGZ, or a MacOS installer. The cpack package config file will then chose the correct components to use. In a later point this should make it possible to build these with `make packages` and the ugly iteration with calling cmake between each package would be obsolete. While this solution is a bit more bloated, it is also much more flexible and it will be much easier to use. Another benefit is, that this will get rid of all warnings during a cpack run
2019-02-28 12:17:11 +08:00
fdb_install(TARGETS fdbcli DESTINATION bin COMPONENT clients)