Hi David!
There is no difference in building static and dynamically linked library as
part of qmake project as such.
It's hard to say what is the problem without seeing project files. My guess
there is wrong path in one of variables added to INSTALLS qmake variable
~Daniil
On Sat, Aug 6, 2011 a
Thanks, Daniil! This is nearly working.
I structured my directories as you advised. Everything builds and the app
links with lib. There is an executable, oh-my/app/app.
Then some task called "copydeploymentfolders" is invoked and it fails. The
output is:
Copying application data...
cp: cann
On Friday, August 05, 2011 05:38:40 PM Ville M. Vainio wrote:
> So I guessed correctly; your rationale for using a library is wrong
> ;-). You are introducing a bunch of deployment headaches for the sake
You're right, Ville, I am introducing deployment headaches. Those headaches
shouldn't be ther
So I guessed correctly; your rationale for using a library is wrong
;-). You are introducing a bunch of deployment headaches for the sake
of having a "reusable unit", which is not in fact reused by other
applications. In general, libraries should only be introduced when
your module is part of the o
Hi David!
This is how you directory structure should look,
you have only one project with name oh-my and it contains one
application and one library
$ tree oh-my
oh-my
├── app
│ ├── app.cpp
│ ├── app.h
│ └── app.pro
├── lib
│ ├── lib.cpp
│ ├── lib.h
│ └── lib.pro
└── oh-my.pro
2 dire
Thanks to Danil, Ville, and Christian for taking the time to answer my call
for help.
On Thursday, August 04, 2011 06:16:16 AM Daniil Ivanov wrote:
> I agree that three project files are the way to go:
> ...
> This is how you declare your library for your application
> http://doc.qt.nokia.com
