On 15.01.10 11:02:53, Michael Jackson wrote:
>
> On Jan 13, 2010, at 4:58 PM, Andreas Pakulat wrote:
>
> >On 13.01.10 13:34:34, clin...@elemtech.com wrote:
> >>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
On Jan 13, 2010, at 4:58 PM, Andreas Pakulat wrote:
On 13.01.10 13:34:34, clin...@elemtech.com wrote:
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.
Thats one way to do it, but appar
On Jan 13, 2010, at 4:58 PM, Andreas Pakulat wrote:
On 13.01.10 13:34:34, clin...@elemtech.com wrote:
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.
Thats one way to do it, but appare
On 13.01.10 13:34:34, clin...@elemtech.com wrote:
> 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.
Thats one way to do it, but apparently not the safest. Qt's SDK binary
package has a s
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.part...@kitware.com]
> > Sent: We
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.part...@kitware.com]
Sent: Wednesday, January 13, 2010 1:01 PM
To: James Willis
nesday, January 13, 2010 1:01 PM
To: James Willis
Cc: cmake@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
The definitive, unambiguous way to do this is to:
set(QT_QMAKE_EXECUTABLE "/full/path/to/qmake")
before:
find_package(Qt4)
Changing the value of QT_QMAKE_EXECUTABLE and then re-executing
find_package(Qt4) is supposed to change all associated Qt variables to match
the corresponding qmake.
On Wed
On 2010-01-13 14:03-0500 Michael Jackson wrote:
SEt the QT_QMAKE_EXECUTABLE variable.
Or put the appropriate version of qmake on your PATH.
Alan
__
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrow
On Wed, Jan 13, 2010 at 12:07:47PM -0600, James Willis wrote:
> 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 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 wrote:
> Is there any good way of telling findqt (I don't really care about findqt3)
> where to
SEt the QT_QMAKE_EXECUTABLE variable.
_
Mike Jackson mike.jack...@bluequartz.net
BlueQuartz Softwarewww.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Jan 13, 2010, at 1:07 PM
On Wed, Jan 13, 2010 at 1:07 PM, James Willis 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
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 hav
Hello Clinton,
I cleaned and rebuild my Qt version and now everything works fine. As
you said, I had a mix of static and dynamic libraries in the same directory.
Thanks.
Did you build both static and shared Qt and install it in the same place?
That would produce a bad instal
Did you build both static and shared Qt and install it in the same place?
That would produce a bad install of Qt. That might explain why you
have both libQtXml.a and libQtXml4.a
Clint
Yes, I have both versions, but in different directories.
I'll try clean the directory and reco
On Aug 4, 2008, at 8:34 AM, Vitor Vasconcelos Araujo Silva wrote:
Hello guys,
I have one project is compiling and linking propertly.
When I tried to include this project in a bigger project, it's not
correctly linking.
I generated both using CMAKE_VERBOSE_MAKEFILE:bool=tr
Hello guys,
I have one project is compiling and linking propertly.
When I tried to include this project in a bigger project, it's not
correctly linking.
I generated both using CMAKE_VERBOSE_MAKEFILE:bool=true and I
eliminated all differences in the compile and link commands,
A Dijous 10 Juliol 2008, Olaf Peter va escriure:
> Hi,
>
> it would be great if FindQt (resp. FindQt4) would support a user file
> extension for QT4_WRAP_UI, e.h. hpp for the ui header. *.hpp is a common
> C++ header extension as I use it for my code.
Since cmake 2.4.8 you have the OPTIONS paramet
Hi,
it would be great if FindQt (resp. FindQt4) would support a user file
extension for QT4_WRAP_UI, e.h. hpp for the ui header. *.hpp is a common
C++ header extension as I use it for my code.
Thanks,
Olaf
___
CMake mailing list
CMake@cmake.org
http://w
20 matches
Mail list logo
