On Wednesday 24 November 2010 17:11:52 David Cole wrote:
> I am not a Qt expert. But to the best of my knowledge, dealing with
> the moc, ui and qrc files and such is best handled by the QT4_* macros
> as demonstrated in the example that I already pointed you to*.
>
thanks problem sorted
On Wednesday 24 November 2010 17:35:16 John Clayton wrote:
> Woops, I meant the
>qt4_wrap_cpp
> macro.
thanks v helpful
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
P
I'm seeing a reproducible failure generating "Visual Studio 10" output
on a system with the following installed:
CMake 2.8.2
CMake 2.8.3
Visual Studio 2005
Visual Studio 2010
Program Files\Microsoft SDKs\Windows
v6.1
v7.0A
v7.1
To keep everything sane I use command files to set environmen
On Wednesday 24 November 2010, David Cole wrote:
> On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer wrote:
> >> On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer wrote:
> In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which
> helps
> with
> creating a basic versio
2010/11/24 David Cole :
> On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe wrote:
>> On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
>>> On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer wrote:
>>> > So I think it is _really_ necessary to go through all the CMake
>>> > documentation item
2010/11/24 Dominique Belhachemi :
>> The ${CMAKE_SOURCE_DIR}/copytree.cmake script simply looks like:
>>
>> FILE(COPY ${SRC} DESTINATION ${DST} PATTERN .svn EXCLUDE)
>>
> Thanks, I will see if this works for me.
>
>> Because FILE(COPY ...) copies files and directories only if they are new
> Does it
On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe wrote:
> On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
>> On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer wrote:
>> > So I think it is _really_ necessary to go through all the CMake
>> > documentation items and add a line about when wh
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
> On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer wrote:
> > So I think it is _really_ necessary to go through all the CMake
> > documentation items and add a line about when which feature was added.
> Adding that information in the docu
On Wed, 2010-11-24 at 10:55 +0100, Michael Hertling wrote:
> On 11/24/2010 04:44 AM, Dominique Belhachemi wrote:
> > Hello,
> >
> > I am using the following command in my CMakeLists.txt file to copy a
> > directory with all sub-directories from the source tree to a directory
> > in the binary tree
Woops, I meant the
qt4_wrap_cpp
macro.
Sent from my iPhone
On Nov 24, 2010, at 7:09 PM, luxInteg wrote:
> On Wednesday 24 November 2010 16:33:24 David Cole wrote:
>> The example that demonstrates how to use BundleUtilities contains a Qt
>> app. See the CMakeLists file in that project for c
See the
qt4_wrap_ui
macro
Sent from my iPhone
On Nov 24, 2010, at 7:09 PM, luxInteg wrote:
> On Wednesday 24 November 2010 16:33:24 David Cole wrote:
>> The example that demonstrates how to use BundleUtilities contains a Qt
>> app. See the CMakeLists file in that project for clues about how to
On Wed, Nov 24, 2010 at 1:09 PM, luxInteg wrote:
> On Wednesday 24 November 2010 16:33:24 David Cole wrote:
>> The example that demonstrates how to use BundleUtilities contains a Qt
>> app. See the CMakeLists file in that project for clues about how to
>> structure a Qt application.
>>
>> See also
On Wednesday 24 November 2010 16:33:24 David Cole wrote:
> The example that demonstrates how to use BundleUtilities contains a Qt
> app. See the CMakeLists file in that project for clues about how to
> structure a Qt application.
>
> See also CMake itself, in the CMake/Source/QtDialog. And ParaVie
On Wed, Nov 24, 2010 at 12:11:56PM +0100, Micha Renner wrote:
>
> > SET(CMAKE_INSTALL_PREFIX "/foo/bar" CACHE PATH "Foo install prefix")
> >
> > So, without the test to CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT,
> > and without the FORCE option.
>
> No, as I mentioned, there was an article of
The BundleUtilities example may be found here, by the way:
http://www.cmake.org/Wiki/BundleUtilitiesExample
(Sorry for forgetting the link on the original reply...)
On Wed, Nov 24, 2010 at 11:33 AM, David Cole wrote:
> The example that demonstrates how to use BundleUtilities contains a Qt
> app
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer wrote:
>> On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer wrote:
In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which
helps
with
creating a basic version-info file which should be installed along with
the
>>>
> On Wed, Nov 24, 2010 at 12:25 PM, luxInteg wrote:
>> Greetings,
>>
>> I am learning cmake. I am now having a go at learning to compile a qt4
>> project wuth cmake. I am starting with qt-4.6.2 and I want to play with
>> compiling a small project into a library.
>>
>>
>> From what I
> On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer wrote:
>>> In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which
>>> helps
>>> with
>>> creating a basic version-info file which should be installed along with
>>> the
>>> Config-file.
>>> It consists of MacroWriteBasicCMakeVersionFil
The example that demonstrates how to use BundleUtilities contains a Qt
app. See the CMakeLists file in that project for clues about how to
structure a Qt application.
See also CMake itself, in the CMake/Source/QtDialog. And ParaView, too
-- it's a Qt app.
Start with the example, though, it's much
Greetings,
I am learning cmake. I am now having a go at learning to compile a qt4
project wuth cmake. I am starting with qt-4.6.2 and I want to play with
compiling a small project into a library.
>From what I can discern most things seem straightforward but some files
seem
On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer wrote:
>> In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which helps
>> with
>> creating a basic version-info file which should be installed along with
>> the
>> Config-file.
>> It consists of MacroWriteBasicCMakeVersionFile.cmake and
On Tuesday 23 November 2010 05:43:17 Michael Hertling wrote:
> On 11/22/2010 10:39 PM, luxInteg wrote:
> > Greetings
> > I am learning cmake
> >
> > I have a small project to be installed in some directory $INSTALLED
> > =/whatever/installed/directory/is
> >
> >
> > I have some files say fi
On Tuesday 23 November 2010 05:37:39 Michael Hertling wrote:
> On 11/23/2010 03:25 AM, luxInteg wrote:
> > Greetings
> >
> >
> > I am learning cmake
> >
> >
> > Compiling alglib (http://www.alglib.net/) (cpp) does not use make
> > It is done simply by a command such as
> >
> > g++ -c *.cpp
Hi,
On 11/23/2010 at 21:25, Alexander Neundorf wrote:
> CMAKE_MODULE_PATH is only for finding Find-modules, not for finding the
> actual packages or Config-files.
> For that you can set CMAKE_PREFIX_PATH. CMake uses each directory contained
> in CMAKE_PREFIX_PATH for all its find_program/file/
On Wednesday 24 November 2010 12:05:49 Reinhard Thies wrote:
> Hi all,
>
> i am trying to crosscompile one of my projects. Iam using some linker flags
> for that:
>
> SET(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -m5307 -Wl,-elf2flt
> -Os -lc")
>
> The following link command will be gene
> In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE() which helps
> with
> creating a basic version-info file which should be installed along with
> the
> Config-file.
> It consists of MacroWriteBasicCMakeVersionFile.cmake and
> BasicFindPackageVersion.cmake.in which you can find in
> htt
Hello,
I am facing a problem here on conflicts between imported targets and
custom targets. Basically I want to override an imported target by a
custom target of the same name. A solution like avoiding clashes
using NAMESPACE on EXPORT doesn't really work for me as the identical
naming is
> SET(CMAKE_INSTALL_PREFIX "/foo/bar" CACHE PATH "Foo install prefix")
>
> So, without the test to CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT,
> and without the FORCE option.
>
> Reason: if someone unsets CMAKE_INSTALL_PREFIX on the command-line with
> -U, CMAKE_INSTALL_PREFIX will default to
Hi all,
i am trying to crosscompile one of my projects. Iam using some linker flags
for that:
SET(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -m5307 -Wl,-elf2flt -Os
-lc")
The following link command will be generated, but I need the -lc option at the
end of t
>>> On 23-11-2010 at 15:37, in message
<1290523061.2001.8.ca...@gildemeister-2>,
Micha Renner wrote:
> Am Dienstag, den 23.11.2010, 15:01 +0100 schrieb Michael Wild:
>> On 11/23/2010 02:33 PM, Micha Renner wrote:
>> > Am Dienstag, den 23.11.2010, 14:01 +0100 schrieb
tomas...@sbc.su.se:
>> >> Dear
On 11/24/2010 04:44 AM, Dominique Belhachemi wrote:
> Hello,
>
> I am using the following command in my CMakeLists.txt file to copy a
> directory with all sub-directories from the source tree to a directory
> in the binary tree.
>
> file(COPY ${SRCDIR}
> DESTINATION ${CMAKE_BINARY_DIR}/${DSTDIR
31 matches
Mail list logo
