[CMake] FindQt in a Specific place?

[clinton at elemtech.com]

I've also seen people put a qt.conf file in the Qt installation, to override the compiled-in paths.
That's probably how its done by the Windows installer.

Clint

----- Michael Jackson <mike.jackson at bluequartz.net> wrote:
> Um, yea, you don't want to do that, change the location of the Qt  
> libraries after they are built in one location. On Windows, the only  
> way you can do that (to my knowledge) is to use the MinGW precompiled  
> binaries from Nokia. When the installer runs all the paths are updated  
> for the install location. As far as I can tell, Nokia has not released  
> the installer build scripts for Qt built under Visual Studio. You seem  
> to need a commercial license for that.
> 
>   So, With Qt, Pick a location where EVERYONE can have Qt installed,  
> build it in THAT location, then you can move the installation from  
> computer to computer. Yes, it sucks.
> _________________________________________________________
> Mike Jackson                  mike.jackson at bluequartz.net
> 
> 
> On Jan 13, 2010, at 3:07 PM, James Willis wrote:
> 
> > So:
> > set (QT_QMAKE_EXECUTABLE "${mySrc}/ExternalLibs/Qt/qt_current/bin/ 
> > qmake")
> >
> > This initially worked.  But only initially.  Then I did something  
> > dastardly: I got rid of the original place I compiled the libraries  
> > -- which qmake still somehow knows despite being compiled with -no- 
> > rpath.
> >
> > Now I get this error:
> > Warning: QT_QMAKE_EXECUTABLE reported QT_INSTALL_LIBS as /home/ 
> > myName/qt-everywhere-commercial-src-4.6.0/Release/lib
> > Warning: /home/myName/qt-everywhere-commercial-src-4.6.0/Release/lib  
> > does NOT exist, Qt must NOT be installed correctly.
> > CMake Error at /home/jwillis/cmake-2.8.0/Modules/FindQt4.cmake:673  
> > (MESSAGE):
> >  Could NOT find QtCore header
> >
> > I also tried Tyler's idea, which fails in exactly the same way, with  
> > the same error.
> >
> > The idea here is my group has people who may want to compile the  
> > code elsewhere on various different machines without installing any  
> > libraries.  We're dependent on a bunch right now, and it's a pain  
> > for each developer to have to get the right version of the right  
> > libraries, in the right order, to compile on their machine.  So we  
> > just stick already compiled versions in a seperate libs  
> > directories.  And no, we'd actually prefer their location set in the  
> > cmakefile so we can change centrally when we decide to upgrade  
> > libraries.
> >
> > Thanks for the help so far, but I'm still hacking away at the moment.
> >
> > --James
> >
> > ________________________________________
> > From: Dave Partyka [dave.partyka at kitware.com]
> > Sent: Wednesday, January 13, 2010 1:01 PM
> > To: James Willis
> > Cc: cmake at cmake.org
> > Subject: Re: [CMake] FindQt in a Specific place?
> >
> > I think if you set these two variables you will get the same desired  
> > result.
> >
> >
> > set(DESIRED_QT_VERSION 4)
> > set(QT_QMAKE_EXECUTABLE /home/qt/4.6.0/bin/qmake)
> >
> > On Wed, Jan 13, 2010 at 1:07 PM, James Willis <JWillis2 at lgc.com<mailto:JWillis2 at lgc.com 
> > >> wrote:
> > Is there any good way of telling findqt (I don't really care about  
> > findqt3) where to find Qt?
> >
> > Like say you did:
> > set(QT_QMAKE_LOCATION /home/myself/qt4.6.0/bin)
> > so that I later upgrade and do:
> > set(QT_QMAKE_LOCATION /home/myself/qt4.6.1/bin) later without having  
> > to muck with my path, but still have findQt find Qt there?
> >
> > I was looking at writing such a feature, if it's not there, and if  
> > you'd be willing to take it as a patch.
> >
> > --James
> >
> >
> > ----------------------------------------------------------------------
> > This e-mail, including any attached files, may contain confidential  
> > and privileged information for the sole use of the intended  
> > recipient.  Any review, use, distribution, or disclosure by others  
> > is strictly prohibited.  If you are not the intended recipient (or  
> > authorized to receive information for the intended recipient),  
> > please contact the sender by reply e-mail and delete all copies of  
> > this message.
> > _______________________________________________
> > Powered by www.kitware.com<http://www.kitware.com>
> >
> > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.cmake.org/mailman/listinfo/cmake
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.cmake.org/mailman/listinfo/cmake
> 
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake