[CMake] CMake and Visual Studio configurations

Hi, When we choose "Debug" or "Release" configuration in Visual Studio, is there a way for CMake to apply different compilations / linking rules? For what I have seen on the mailing list, we can set "CMAKE_CONFIGURATION_TYPES" to only use a particular configuration in VS, but what if we want to u

Re: [CMake] CMake 2.8.0 built on OS X crashes on Startup.

Reported as bug number 1 Hey, do I get some sort of Cookie or something for having bug number 10,000? At least it will be easy to remember the bug number. _ Mike Jackson mike.j

Re: [CMake] CMake 2.8.0 built on OS X crashes on Startup.

Sorry No Patch but here is what needs to be inserted into $CMAKE_SOURCE/Source/QtDialog/CMakeLists.txt. I'll put some context around it for David or Bill to more easily find the place: IF(APPLE) SET(CMAKE_POSTFLIGHT_SCRIPT "${CMake_BINARY_DIR}/Source/QtDialog/postflight.sh") SET(C

Re: [CMake] Build only what you need in third party libs

I _think_ you _might_ be able to set the BUILD_PROJECTS to "file_system;system" then do the "add_subdirectory()". Give it a shot and see what happens. _ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Software

[CMake] Build only what you need in third party libs

I have used boost jam before and there was a mechanism to build only what you need by specifying dependencies within the boost libraries. bjam would then run off calculate deps and build only what I needed. In CMake is there such a feature to specify a third party library and specify only the targ

Re: [CMake] Runtime directory / staging question

On Sat, Dec 05, 2009 at 01:38:40PM -0600, Brian Davis wrote: > Can you provide an example of how you use this. I would appreciate it. > > I echoed these to the screen and they do not seem to be set. Should I > expect them to be? > > PREFIX = > > IMPORT_PREFIX = PREFIX and IMPORT_PREFIX are pr

Re: [CMake] Runtime directory / staging question

Tyler, Can you provide an example of how you use this. I would appreciate it. I echoed these to the screen and they do not seem to be set. Should I expect them to be? PREFIX = IMPORT_PREFIX = CMAKE_HOST_SYSTEM = Windows-6.1 CMAKE_HOST_SYSTEM_NAME = Windows Thanks, Brian On Fri, Dec 4, 2

Re: [CMake] CMake 2.8.0 built on OS X crashes on Startup.

It would be nice to have a function allowing one to override/extend the default choice (which AFAIK is determined by asking otool about link-dependencies). Perhaps something like this: set_external_framework_properties( ${QT_QTGUI_LIBRARY} PROPERTIES REQUIRE Resources/qt_menu.nib DESTINAT

Re: [CMake] A bug for Code::Blocks MinGW?

Well, certainly you could put your project in a path without any spaces in the path name until the bug is fixed... On Fri, Dec 4, 2009 at 8:17 PM, Song Zhiwei wrote: > Before the bug fixed, is there any way inside CMake to add " > around the filename? Use special commands? > > Zhiwei > > 2009/1

Re: [CMake] CMake 2.8.0 built on OS X crashes on Startup.

That's what I meant ;-) On 5. Dec, 2009, at 15:25 , Mike Jackson wrote: Qt 4.5 Carbon does not require the qt_menu.nib to be in the final shipping application which is why all the previous scripts work. But then again, you probably knew that... ;-) __

Re: [CMake] CMake 2.8.0 built on OS X crashes on Startup.

Qt 4.5 Carbon does not require the qt_menu.nib to be in the final shipping application which is why all the previous scripts work. But then again, you probably knew that... ;-) _ Mike Jackson mike.jack...@bluequartz.net On Sa

Re: [CMake] CMake 2.8.0 built on OS X crashes on Startup.

On 5. Dec, 2009, at 14:47 , Mike Jackson wrote: Probably what is going to happen is there will be "special" case copies from frameworks into bundles. In this case, copying the qt_menu.nib and any qt.conf is probably specific to QtGui.framework. At this point I there is probably 2 things that ne

Re: [CMake] CMake 2.8.0 built on OS X crashes on Startup.

Probably what is going to happen is there will be "special" case copies from frameworks into bundles. In this case, copying the qt_menu.nib and any qt.conf is probably specific to QtGui.framework. At this point I there is probably 2 things that need to happen. A bug report for the QtGui resources