Getting Started with Qt Editions

The Qt editions of our products include everything needed to integrate them into cross-platform applications built with the Qt Framework. This guide will provide essential information to help you get started using our components in Qt Creator. Specifically, we'll be discussing how to integrate components from our IPWorks toolkit into an application built with Qt 5.


Adding the Components to Your Project

Each of our Qt toolkits include native libraries for Windows, Linux, and macOS; as well as the .h and .cpp files necessary to use them in a Qt project. You'll find these files in the following places within the product's installation directory (individual component files have been collapsed into [component] for brevity):

|       q[component].cpp
|       q[component].h
|       qipworks.cpp
|       qipworks.h
|       qipworkskey.h
|   +---linux
|   |
|   \---windows
|           qtipworks20.dll
|           qtipworks20.lib
|           qtipworks20s.lib
    |       libqtipworks.20.0.dylib

Qt Creator includes an "Add Library..." wizard, however it is simpler to add our components to your project by modifying the .pro file directly (especially for cross-platform projects). To begin, open your project's .pro file in Qt Creator. Before anything else, we're going to add some convenience variables to the .pro file to help simplify the rest of the modifications.

First, we'll add a variable containing the path to the installation directory (or wherever you're storing the include, lib, and lib64 folders shown above). We'll call this variable PRODDIR, which is the same name used by the .pro files in our demo projects. The path stored in this variable must not contain any spaces, otherwise qmake will generate a makefile with malformed targets, preventing your project from building correctly.

It is recommended to install or copy the required files to a path which does not contain spaces. However, if the path does have spaces using the "short path" will ensure the path does not have spaces. On Windows, you can use the command prompt or PowerShell snippet shown below to obtain a "short path" for the installation directory. Note that short paths never contain spaces, but can vary from machine to machine. If the .pro file will be used on multiple machines, it is recommended to copy the include, lib, and lib64 folders to a different location without spaces.

CMD> for %I in ("C:\Program Files\nsoftware\IPWorks 2020 Qt Edition") do @echo %~sI

PS> $(New-Object -com Scripting.FileSystemObject).GetFolder("C:\Program Files\nsoftware\IPWorks 2020 Qt Edition").ShortPath()

Once you have a path without spaces, add a line like the one below to your .pro file. Keep in mind that relative paths will also work; for example, our demos set PRODDIR to ../...


In addition to PRODDIR, we'll declare a few more convenience variables: LIBDIR, PLATDIR, and LIBNAME. To declare these variables, add the following lines to your .pro file:

greaterThan(QT_MAJOR_VERSION, 4) { TARGET_ARCH = $$${QT_ARCH} } else { TARGET_ARCH = $$${QMAKE_HOST.arch} }
contains(TARGET_ARCH, x86_64) { LIBDIR = lib64 } else { LIBDIR = lib }

win32 {
  PLATDIR = windows
  LIBNAME = qtipworks20
} unix:!macx {
  PLATDIR = linux
  LIBNAME = qtipworks
} macx {
  PLATDIR = mac
  LIBNAME = qtipworks.20.0

Now that all of the convenience variables have been declared, we can make the modifications necessary to add the components to the project. For example purposes, assume we want to make use of the HTTP and XML components in our application. To do so, we need to tell qmake where to find the .h and .cpp files for those components, as well as the IPWorks library itself. To do this, add the following lines to your .pro file:

HEADERS += $$${PRODDIR}/include/qhttp.h $$${PRODDIR}/include/qxml.h
SOURCES += $$${PRODDIR}/include/qhttp.cpp $$${PRODDIR}/include/qxml.cpp
LIBS += -L"$$${PRODDIR}/$$${LIBDIR}/$$${PLATDIR}" -l$$${LIBNAME}
unix:!macx: LIBS += -lssl -lcrypto
DEPENDPATH += $$${PRODDIR}/include

At this point, we've finished the basic steps needed to add the library and components to the project, and you should be able to compile your application successfully on all platforms. (On Linux, ensure that the shared library has been "installed" so that it's available to the linker at link-time, and the executable at run-time.)

Note: On Windows, if your application is compiled with the dynamic library (qtipworks20.lib) rather than the static library (qtipworks20s.lib), you'll need to ensure that the product's DLL is available at run-time. An easy way to do this is to have qmake copy the DLL to the output directory each time it builds your application. You can make this happen by adding the following lines to the end of the win32 {...} section we added to the .pro file earlier:

win32 {
  LIBPATH = "$$${PRODDIR}/$$${LIBDIR}/$$${PLATDIR}/$$${LIBNAME}.dll"
  CONFIG(debug, debug|release) { VARIANT = debug } else { VARIANT = release }
  copydll.commands = $(COPY_FILE) \"$$$replace(LIBPATH, /, \\)\" \"$$$replace(OUT_PWD, /, \\)\\$$${VARIANT}\"
  first.depends = $(first) copydll
  QMAKE_EXTRA_TARGETS += first copydll
} unix:!macx {

Using the Components

Once the components are available in your project, you can make use of them like you would any other complex type, refer to product documentation for more information about each component's API. To handle a component's events, your application can do one of the following:

  1. Connect slots to the component's signals.
  2. Subclass the component and override its event emitter functions directly.

Signals & Slots

Using signals and slots to handle component events works the same way it does anywhere else in a Qt application: your class implements slot functions, and then uses Qt's connect() function to wire them up to the appropriate signal functions exposed by the component. In GUI applications, you can even "attach" the components to the widget hierarchy in order to leverage automatic connections.

Here's a small example of using automatic connections based on the httpurl demo included with IPWorks. By attaching the HTTP component instance to the widget hierarchy, the on_http1_Transfer() slot (whose name follows the on_[object name]_[signal name] naming convention required for automatic connections to work) is automatically connected to the http1 object's Transfer() signal.

 * httpurl.h (some content omitted for brevity)
#include <QMainWindow>
#include "qhttp.h"

namespace Ui { class httpurl; }

class httpurl : public QMainWindow

  httpurl(QWidget *parent = nullptr);

private slots:
  void on_btnGet_clicked();
  void on_http1_Transfer(HTTPTransferEventParams *e);

  Ui::httpurl *ui;
  HTTP http1;
 * httpurl.cpp (some content omitted for brevity)
#include "httpurl.h"
#include "ui_httpurl.h"

httpurl::httpurl(QWidget *parent) : QMainWindow(parent), ui(new Ui::httpurl)
  // Attach our components to the widget hierarchy so that their signals get connected to our slots.


void httpurl::on_btnGet_clicked()

void httpurl::on_http1_Transfer(HTTPTransferEventParams *e)


In some cases, you may find it more convenient to handle a component's events directly. To do this, simply subclass the component in question and override the event emitter function(s) you wish to handle. Event emitter functions are those whose names match the Fire[Event] pattern; their default implementation, which can be seen in a component's .cpp file, is simply to emit the corresponding signal.

#include <QCoreApplication>
#include "qhttp.h"

class MyHTTP : public HTTP {
  virtual int FireStartTransfer(HTTPStartTransferEventParams *e) override {
    printf("Transfer started.\n");
    return 0;

  virtual int FireEndTransfer(HTTPEndTransferEventParams *e) override {
    printf("Transfer complete.\n");
    return 0;

int main(int argc, char *argv[]) {
  QCoreApplication a(argc, argv);
  return 0;

We appreciate your feedback.  If you have any questions, comments, or suggestions about this article please contact our support team at