Creating the single executable of Qt App which uses the OpenCV

rohaanembedded · 01-21-2014, 12:39 AM

Dear sir,

I am using Qt Creator 2.2.1 based on Qt 4.7.4 and opencv-2.4.6.1 to develop app which shows images on my qt app and some basic image manipulation.

As I am done with the basic app i want to make it deployable utility but as i am using the opencv it shows dependency of opencv not installed.
how can i make single executable of this app so that PC on which it is going to be used will not need to install Qt and OPenCV.

I Hvae tried some changes in qt project .pro file like added

Code:

CONFIG +=static

.pro file

Code:

QT       += core gui

TARGET = PIV
TEMPLATE = app


SOURCES += main.cpp\
        mainwindow.cpp

HEADERS  += mainwindow.h

FORMS    += mainwindow.ui

# include own lib
INCLUDEPATH += /home/usb/include/
INCLUDEPATH += /home/usb/FPR/src/

LIBS += -L/home/usb/FPR/lib -lsyn -L /home/usb/lib -lcyusb # .so files

LIBS += `pkg-config opencv --libs`

CONFIG += static

please let me know the procedure to make this single executable.
i read some of the articles related with this but didnt got specific idea if one has done this please help me

Note:
I am using
Distributor ID: Ubuntu
Description: Ubuntu 11.10
Release: 11.10
Codename: oneiric

Regards,
Rohaan

rtmistler · 01-22-2014, 04:02 PM

I have always had trouble "deploying" Qt applications that were non-static. As a result I always configure Qt and make Qt static.

This means that you'd need to configure the Qt toolkit and remake it using the static argument.

In your Qt directory where the source for Qt is located:

Code:

./configure <all other arguments you've already used> -static
make
sudo make install

Not sure if you wish to take that step, but that's what I've done to be able to give out Qt apps and just give out the final binary executable without needing a bunch of libraries or other dependencies.

Note also: I have config.status which shows the last form of my ./configure command. Well, sorry either config.status or config.last. I think I copied one as a former backup and forget which one Qt natively creates. But my point is Qt does create a record of your last ./configure argument so you can see what you did ... two years ago (Yes! That's how long it's been since I've rebuilt my Qt :-) )