[Qt-interest] Build problem when using QtSingleApplication solution

[Ross Driedger]

On Wed, 18 Nov 2009 05:23:50 -0500, <qt-interest-request at trolltech.com>  
wrote:

Hey Marcus,

>> Providec the .pri is referred to in your .pro, qmake should put the
>> necessary references to the files into the Makefiles.  What version are
>> you running?  I'm using 4.5.1 on windows and 4.5.2 on Mac/*NIX (both
>> commercial) with no problems.
> Thats what I thought - unfortunately we're building our app inside
> Visual Studio so we're not using the makefiles or pri/pro files I think.

I generally start my projects as .pro files and, if I feel the need to, I  
import them into VS (I'm using 2005 with the Qt integration). Perhaps I'm  
a bit 'old-school', believing that programmers should be able to manage  
just fine with just a command prompt, a debugger like gdb and something as  
basic vi for editing files.

OK, perhaps not that extreme.

Doing a quick scan of a project I imported into VS, I could not find the  
place where the .pri is references, although moc_qtsingleapplication.cpp  
appears in the Generated Files for the project, the qtsingleapplication.h  
shows up in the Header Files and the two .cpp files,  
qtsingleapplication.cpp and qtsingleapplication_win.h, are in the Source  
Files for the project.

Truth be told, I am no big fan of Visual Studio, so I'm not all that keen  
on upgradinging that part of my tool chain.

>> I'm a bit confused.  You are using the solution as part of a DLL?  Isn't
>> the point of a DLL to serve a number of different possible applications
>> and application instances?
> Its only being built as a dll to solve the LGPL problem - we cant
> statically link against it or include the code inside our codebase
> without violating the LGPL (which is why I raised the question about the
> moc file).

That explains it.  Thanks for clarifying.

Sorry I couldn't give you more information. :(

Ross

-- 
"Life without music would be a mistake. "
Friedrich Nietzsche


Ross Driedger
ross_at_earz.ca