Hello folks,
I had a question a long time ago about the qt4_wrap_cpp and the
target_include_directories commands.
To explain the problem, I wanted to use target_include_directories to
add include directories to dependent target easier. However I really
wanted to use qt4_wrap_cpp and not AUTOMOC
David Demelier wrote:
Hello folks,
I had a question a long time ago about the qt4_wrap_cpp and the
target_include_directories commands.
To explain the problem, I wanted to use target_include_directories to
add include directories to dependent target easier. However I really
wanted to
If you run moc on Main.h, which includes Dum.h, moc doesn't even open Dum.h
to scan its contents.
That tells me there is no way that moc would be required to rescan Main.h if
Dum.h is modified.
Clint
On Oct 10, 2012, at 10:32 PM, Miller, Frank wrote:
Greetings,
Suppose we have a header
Hi,
in addition to that, moc does not support ifdef'ing of code it needs
to look at (it does not have a preprocessor at all, only knows a few
select define's), so there can also not be a case of Dum.h setting
defines which cause moc to generate different code for Main.h.
I'd say qmake is just
Greetings,
Suppose we have a header file, Dum.h, that is included by another header
file, Main.h, and Main.h needs to be processed with the qt moc tool.
When Dum.h changes, should we rerun moc on Main.h?
QMake says yes. CMake, using QT4_WRAP_CPP, says no.
I am inclined to believe qmake on this
Hello
how to control where the generated moc files go ?
I am using this macro like this :
FILE(GLOB MOC_HEADERS
moc/*.h )
QT4_WRAP_CPP(out_moc_files ${MOC_HEADERS})
And the generated files are going in my CMAKE_BINARY_DIR.
What to do if I want the generated files to go to
Do I actually need moc generated files per build comfiguration?
On Mon, Nov 2, 2009 at 4:21 PM, elizabeta petreska
elizabeta.petre...@gmail.com wrote:
Hello
how to control where the generated moc files go ?
I am using this macro like this :
FILE(GLOB MOC_HEADERS
moc/*.h )
On Nov 2, 2009, at 1:41 PM, elizabeta petreska wrote:
Do I actually need moc generated files per build comfiguration?
No you don't. The output from moc is identical for all build
configurations.
Clint
On Mon, Nov 2, 2009 at 4:21 PM, elizabeta petreska
elizabeta.petre...@gmail.com
Thank you for the reply
then why when I am building my project with qmake, the moc generated files
are going in my debug and release folders? It shoud not be like so, if the
moc output is identical right? or I am missing something
On Tue, Nov 3, 2009 at 1:53 AM, Clinton Stimpson
In what version of CMake was QT4_WRAP_CPP added? I'm working on a
project that relies on this command, and I'd like to set
CMAKE_MINIMUM_REQUIRED appropriately.
-Zack
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
It was added in CMake 2.2, which is when FindQt4.cmake was introduced.
Clint
Zack Galbreath wrote:
In what version of CMake was QT4_WRAP_CPP added? I'm working on a
project that relies on this command, and I'd like to set
CMAKE_MINIMUM_REQUIRED appropriately.
-Zack
Hi Zack,
On Monday 11 May 2009, Zack Galbreath wrote:
In what version of CMake was QT4_WRAP_CPP added? I'm working on a
project that relies on this command, and I'd like to set
CMAKE_MINIMUM_REQUIRED appropriately.
KDE 4.0 (released January last year) and 4.1 require CMake 2.4.5, so you can
Hi,
When using QT4_WRAP_CPP in CMakeLists.txt file and using Visual Studio 8 2005
as the generator the header files which have to be moced are not displayed in
the folder structure of VS. I tryed to force to display them via SOURCE_GROUP
but had no success. Is this a bug?
Thanks in advance,
13 matches
Mail list logo
