Mercurial > hg > piper-cpp
view vamp-client/client.pro @ 116:d15cb1151d76
Add JSON support directly to the server. Had hoped to avoid this (using Capnp as canonical in the server and then converting externally as necessary) but it's just too useful for debugging purposes when bundled with client app
author | Chris Cannam <c.cannam@qmul.ac.uk> |
---|---|
date | Thu, 27 Oct 2016 11:39:41 +0100 |
parents | 247d8d533a9c |
children | 1902e6db5b61 |
line wrap: on
line source
TEMPLATE = app CONFIG += qt stl c++11 exceptions console warn_on QT -= xml network gui widgets !win32 { QMAKE_CXXFLAGS += -Werror } OBJECTS_DIR = ../o MOC_DIR = ../o VAMPSDK_DIR = ../../vamp-plugin-sdk PIPER_DIR = ../../piper QMAKE_CXXFLAGS = -I$$VAMPSDK_DIR -I.. LIBS += -lcapnp -lkj -lvamp-hostsdk # Using the "console" CONFIG flag above should ensure this happens for # normal Windows builds, but this may be necessary when cross-compiling win32-x-g++:QMAKE_LFLAGS += -Wl,-subsystem,console TARGET = client SOURCES += \ client.cpp \ ../vamp-capnp/piper-capnp.cpp HEADERS += \ ProcessQtTransport.h \ CapnpRRClient.h \ Loader.h \ PluginClient.h \ PluginStub.h \ AutoPlugin.h \ SynchronousTransport.h