[CMake] static Qt linking while building other DLLs

Hey, I'd like to hard-link Qt in my application, while at the same time allowing some of my other libraries to build as DLLs. Last time I looked cmake just had a single 'either or' option for building either as shared libraries or without. Is there some way to do a mixed build like this, and more

[CMake] CMake Xcode SCC

Hi all, I'm using Xcode 3.2.2 and Perforce for my Source Code Control. Whenever I rebuild the Xcode project with cmake, Xcode loses its connection to the source code server and I have to reset it manually. Does anyone have a solution for this? Thanks in advance Glenn

Re: [CMake] qt .qrc file modifications require two builds

Removed the globbing, same exact behavior. Any other ideas? Does this normally work for people? Any examples? G ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep

Re: [CMake] qt .qrc file modifications require two builds

Here's a very short example that demonstrates the problem. This is a CMake file for the states qt 4.6 example (Developer/Examples/Qt/animation/states) #--- PROJECT(states) # the name of your project CMAKE_MINIMUM_REQUIRED(VERSION 2.4.0) FIND_PACKAGE(Qt4 REQUIRED) # find and setup Qt4 for this

Re: [CMake] SDL troubles on Mac OS X

I think the SDL developers are just being a bit too slick. They are setting up SDL for Xcode development where typically you would link to the SDL and then have a Copy Files Phase where you copy the framework into the Application Bundle that resides in the build directory. Its a cultural

[CMake] qt .qrc file modifications require two builds

If I modify my .qrc file, the first build regenerates the cxx output file, but the cxx file itself is not compiled and linked in until I build again. Is there a way to add an additional dependency to allow the system to realize that the cxx file needs a rebuild on the first pass? The CMake script

Re: [CMake] qt .qrc file modifications require two builds

Really? How could it? Suppose I only have 1 qrc file, named foo.qrc: wouldn't these two lines be equivalent? FILE (GLOB my_RESOURCES RELATIVE ${CMAKE_CURRENT_SOURCE_DIR} res/*.qrc ) SET( my_RESOURCES res/foo.qrc) ??? TIA G On Tue, Dec 15, 2009 at 7:15 PM, John Drescher dresche...@gmail.com

[CMake] source_group with XCode?

Hi again, I'm trying to use the source_group command with XCode, and its marginally working, but in a flaky sorta way. I was wondering what other people have any tips. The behavior I'm seeing is: Groups in the form source_group( Name FILES ${source} ) Work OK, they

Re: [CMake] Framework Installation Directory / Framework copying

Thanks Mike, I pretty much got my build process on the Mac working. The thing that took me awhile to understand were the different running contexts that bits of the CMake script are processed within. What I want is a little different than the standard way that things are done in the CMake way

Re: [CMake] where are the output files?

For a Xcode specific solution to this see my specFramework Installation Directory / Framework copying thread. ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep

Re: [CMake] Framework Installation Directory / Framework copying

The subtle thing about the Xcode Environment variables is that your CMake Code is run at Cmake Time which will have no idea about the Xcode variables that are set during a Build Time. Right. But in my case this is OK, because I evaluate the Xcode env variable in my python script which is run

[CMake] Anyone know what foo.moc.rule files are?

I have my Qt project building using CMake, but in the Xcode project I'm seeing references to missing foo.moc.rule files for each moc'd source file. The fact that they are missing doesn't seem to be hurting anything, but I'm wondering what they are, and if they're not needed, how I can get rid of

[CMake] Framework Installation Directory / Framework copying

Hi all, Does anyone have any experience with how to copy a built framework into the application bundle? In Xcode we set the Installation Directory of the Framework to @executable_path/../Frameworks/, then as a post-link phase of building the app we run a python script to copy the built framework

[CMake] where are the output files?

Ok, this is something that I thought was going to be easy, but I really can't figure it out... I've written a python script to smash my private frameworks into my built application, but, I need to know exactly where the frameworks and the app have been built. I know I can control the top-level

[CMake] FindQT4 documentation?

Hi all, Is FindQT4 documented anywhere? I've found it referenced through a few examples, but googling for it mostly yields bug reports rather than information. Thanks! Glenn ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] can't link simple qt example

named main.h. It seems in general putting your Q_OBJECT class defs in a header is required when building Qt projects under CMake... but there's probably some way around it. Cheers G On Fri, Dec 4, 2009 at 8:59 PM, Glenn Hughes ghughes02...@gmail.com wrote: Hello all, I'm just getting going

[CMake] question about QT4_WRAP_CPP

I'm still playing around with the states Qt example, and I've hit something I don't understand: I can get everything working as expected with QT4_AUTOMOC, but not if I use QT4_WRAP_CPP. In the QT4_WRAP_CPP case, it seems the only way to get dependencies set up correctly is to add the MOC output

[CMake] can't link simple qt example

Hello all, I'm just getting going with CMake and qt, and I'm having a bit of a problem. I've assembled pretty much the simplest CMakeLists.txt file I can imagine for a very simple example qt project. (I'm trying to build the qt 4.6 states example using CMake.) When I build, I get the following