view vamp-client/qt/test.pro @ 186:52322dde68ea

Fix erroneous logic for handling step and block size in prior commit

The earlier change had a logical misconception. If PluginStub is
receiving the correct step and block size back from the configure call,
the plugin on the server side must have already been successfully
initialised, as the step and block size are only returned in a
successful configure response. This means the test for a failed
initialise and redo with the correct parameters must be done on the
server side (in LoaderRequests) not the client. The client has a more
complicated job, which is to notice that a *successful* configure had
returned different framing parameters from those passed to the
initialise call, and to pretend that it had actually failed until the
host called again with the correct parameters. We definitely need tests
for this!

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.. -I../..

LIBS += -L/usr/local/lib -lcapnp -lkj -L$$VAMPSDK_DIR -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

macx*: CONFIG -= app_bundle

TARGET = test

SOURCES += \
        test.cpp \
        ../../vamp-capnp/piper-capnp.cpp
        
HEADERS += \
        ProcessQtTransport.h \
        AutoPlugin.h \
        ../CapnpRRClient.h \
        ../Loader.h \
        ../PluginClient.h \
        ../PluginStub.h \
        ../SynchronousTransport.h