[CMake] cmake + Qt4 compilation problem

Hello everyone! I'm trying to compile a simple application using Qt4 with cmake, but I'm stucked in this error: [ 33%] Generating ui_mivgui.h Scanning dependencies of target viewer [ 66%] Building CXX object CMakeFiles/viewer.dir/main.o [100%] Building CXX object CMakeFiles/viewer.dir/mivgui.o

Re: [CMake] cmake + Qt4 compilation problem

Von: Luis Roberto P. Paula Hello everyone! I'm trying to compile a simple application using Qt4 with cmake, but I'm stucked in this error: [ 33%] Generating ui_mivgui.h Scanning dependencies of target viewer [ 66%] Building CXX object CMakeFiles/viewer.dir/main.o [100%] Building CXX

Re: [CMake] cmake + Qt4 compilation problem

Von: Christian Ehrlicher Von: Luis Roberto P. Paula Hello everyone! I'm trying to compile a simple application using Qt4 with cmake, but I'm stucked in this error: [ 33%] Generating ui_mivgui.h Scanning dependencies of target viewer [ 66%] Building CXX object

[CMake] CMAKE ERROR WITH BORLAND

Hi All, I assume it's the right place to raise my query regarding usage of cmake with Borland c++ builder v5.5. I am trying to generate makefile for my source tree with Borland c++ v5.5 compiler using cmake. But when I click on configure button after choosing all the settings like: source

[CMake] Create a rule

Hi, I want to create a rule to transform all files with .pgc extensions to files with .cpp extensions with ecpg executable. Do you any samples ? Thanks. - Jean-Michel Créez votre adresse électronique [EMAIL PROTECTED] 1 Go d'espace de stockage, anti-spam et anti-virus intégrés.

Re: [CMake] Create a rule

Message du 09/09/08 09:49 De : Jean-Michel Caricand [EMAIL PROTECTED] A : cmake@cmake.org Copie à : Objet : [CMake] Create a rule Hi, I want to create a rule to transform all files with .pgc extensions to files with .cpp extensions with ecpg executable. Do you any samples ?

Re: [CMake] MPI modules

Hi Robert, A simpler method to pass the flags would be to set in tou CMakeLists.txt set(CMAKE_BUILD_TYPE None) and then the flags that you pass throught CXXFLAGS variable would be read. Alin -- __ ...if the

Re: [CMake] cmake 2.6 insists on using MSVC x64 even when in 32 bit shell

This problem has been resolved with the kind assistance of Bill Hoffman of Kitware. THe problem of compiling/linking a mixed version of 64/32 bit binaries was caused by my VS containing some 64 bit paths in the 32 bit configuration mode. These paths can be examined using Tools- Options -

[CMake] Clearing all cmake files

I was wondering if there is a standard command to clear all cmake files, including CMakeLists.txt, CMakeCache.txt, the CMakeFiles directory and cmake_install.cmake? ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Clearing all cmake files

If you used an out of source build then you can simply delete the build directory. If you did NOT use an out-of-source build then you are going to have to hand pick through your source directories to find everything that does not belong. With that said CMakeCache.txt is the first obvious

Re: [CMake] Clearing all cmake files

On Sep 9, 2008, at 10:36 AM, Mike Jackson wrote: If you used an out of source build then you can simply delete the build directory. If you did NOT use an out-of-source build then you are going to have to hand pick through your source directories to find everything that does not belong.

Re: [CMake] Clearing all cmake files

I am going to assume then that you DID in fact use an out of source build for your project. Assuming that build directory is called Build the command is: rm -rf Build/ (Linux/Unix/OS X) Use Windows Explorer to delete the entire build tree on Windows. Those are the commands. Granted they

[CMake] Including object/archive/library in a static lib

Hi all, I am trying to _include_ an externally built library B in a static lib A that I'm building with Cmake. For MSVC, I would like it to end up in the LibrarianAdditional Dependencies (and have its path in the Additional Library Directories). Also, this would add some /LIBPATH: and the

Re: [CMake] Clearing all cmake files

I did not use an out of source build, so that of course would simplify things, but I still think that a command like: cmake erase Would be convenient to clear all cmake generated files and roll-back to the scenario *before* 'cmake .' Yes, I can remove files manually but the user is not

Re: [CMake] Clearing all cmake files

And hence the reason to use an out of source build. That alleviates the problem. Now, just in case you are still new to cmake, here is a subtle FYI about out of source builds. The build directory can be a sub directory of your project. MyProject/ src/ includes/ Build ===

[CMake] Compiler varience?

That does help a lot, but I think does not go quite far enough. As I said, there are other things that need to be done such as: - Adjusting warning levels (CMAKE_WARN_LEVEL=(None|Full|Standard) ) - Forcing a 32-bit or 64-bit compile - Allowing for platform-specific builds if possible (ie. don't

Re: [CMake] Compiler varience?

Preston A. Elder wrote: That does help a lot, but I think does not go quite far enough. As I said, there are other things that need to be done such as: - Adjusting warning levels (CMAKE_WARN_LEVEL=(None|Full|Standard) ) - Forcing a 32-bit or 64-bit compile - Allowing for platform-specific

Re: [CMake] ctest puts LD_LIBRARY_PATH into environment impacts sub-runs of cmake/ctest

() for valgrind builds? I've always just done one of the other, but cannot remember why. 3. There used to be a file $BLDTREE/Testing/TAG that had the date string (e.g. 20080909-1705) of the most recent output directory used by ctest. I've been checking for the presence of $BLDTREE/Testing

Re: [CMake] Compiler varience?

Bill Hoffman wrote: Preston A. Elder wrote: That does help a lot, but I think does not go quite far enough. As I said, there are other things that need to be done such as: - Adjusting warning levels (CMAKE_WARN_LEVEL=(None|Full|Standard) ) - Forcing a 32-bit or 64-bit compile - Allowing for

[CMake] creating PackageConfig.cmake and the LOCATION property

I have an outdated version of Mastering CMake book (for CMake version 2.2). Referring to section 6.7 Creating a PackageConfig.cmake file, the configure step contains the following: GET_TARGET_PROPERTY( GROMIT_LIBRARY Gromit LOCATION ) where Gromit is the library target and GROMIT_LIBRARY is

Re: [CMake] ctest puts LD_LIBRARY_PATH into environment impacts sub-runs of cmake/ctest

that had the date string (e.g. 20080909-1705) of the most recent output directory used by ctest. I've been checking for the presence of $BLDTREE/Testing/string_taken_from_TAG/Configure.xml to determine whether a continuous ctest build just the a CVS update and found no changes, or did a CVS update

Re: [CMake] creating PackageConfig.cmake and the LOCATION property

Server Levent Yilmaz wrote: I have an outdated version of Mastering CMake book (for CMake version 2.2). Referring to section 6.7 Creating a PackageConfig.cmake file, the configure step contains the following: GET_TARGET_PROPERTY( GROMIT_LIBRARY Gromit LOCATION ) where Gromit is the

Re: [CMake] Compiler varience?

On Tuesday 09 September 2008, Preston A. Elder wrote: Hey, Is there a module out there that will supply pre-defined flags for different compilers? I made a start on one, but I can't believe I am the first, but a snippet of what I have been making: if (${CMAKE_C_COMPILER_ID} STREQUAL GNU)

Re: [CMake] Clearing all cmake files

This is not possible because you might have more build directories and might not want to delete them all. plus the builddirs are not linked to srcdirs. I still wonder why cmake does let to build a builddir in a non-empty folder... On Tue, Sep 9, 2008 at 6:50 PM, Robert Kubrick [EMAIL