[CMake] Module search paths - distribution precedence

This is a discussion about how to code module search paths, with regard to distribution porting of cmake. The examples below use MacPorts only because that's what I'm working with at the moment. The issue applies to any port of cmake on a specific distribution system (MacPorts, Fink, debian, free

Re: [CMake] VS2010 support

Robert Dailey wrote: Oops! I spoke too fast :) I found this: http://www.cmake.org/pipermail/cmake/2009-May/029660.html But, don't forget about this post: http://www.cmake.org/pipermail/cmake/2009-May/029782.html Your help would be appreciated. -Bill ___

Re: [CMake] Problems with Intel Fortran 11 on Windows XP

Bill, I forgot to provide details for the build case that fails when using IVF 11 with the Visual Studio 9 2008 Generator. Assuming that I have a hacked version of CMake that produces .vfproj files with Version="11.0", the following project will generate a .sln (and .vfproj) file, but the project

Re: [CMake] VS2010 support

Oops! I spoke too fast :) I found this: http://www.cmake.org/pipermail/cmake/2009-May/029660.html On Tue, Jun 2, 2009 at 7:51 PM, Robert Dailey wrote: > Hey guys, > I'm sure you've already started VS2010 support. How is that going? I'd like > to test it out for you if you've already released sup

[CMake] VS2010 support

Hey guys, I'm sure you've already started VS2010 support. How is that going? I'd like to test it out for you if you've already released support for it in 2.7. Let me know! Thanks. ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] Problems with Intel Fortran 11 on Windows XP

Bill, Thanks for offering to look into this problem with Intel Visual Fortran integrated into Visual Studio. We are trying to patch up our CMake files so that we can build using the Visual Studio IDE (NMake Makefiles work fine) and have run into this where Intel Visual Fortran 11.0 (full version,

Re: [CMake] Removing flags added by the Platform modules

You can always replace the file in the modules directory with your own edited version. Mike Jackson Sent from my iPod On Jun 2, 2009, at 19:22, Will Dicharry wrote: We have a problem on AIX with the IBM C++ compiler. In the standard cmake AIX Platform module in cmake-2.6/Modules/Platf

Re: [CMake] Compiling generated Qt resource files?

Eric Lemings wrote: How do I compile a Qt resource file that is generated via a CMake add_custom_command() target? qt4_add_resource() doesn't seem to work as it expects non-generated files. Can you generate it at cmake time instead of build time? ParaView has an example of this. qt4_add_res

[CMake] Removing flags added by the Platform modules

We have a problem on AIX with the IBM C++ compiler. In the standard cmake AIX Platform module in cmake-2.6/Modules/Platform, the following variables are set: SET(CMAKE_PLATFORM_REQUIRED_RUNTIME_PATH /usr/lib /lib) SET(CMAKE_SHARED_LIBRARY_RUNTIME_C_FLAG "-Wl,-blibpath:") The strange thing is

[CMake] Compiling generated Qt resource files?

How do I compile a Qt resource file that is generated via a CMake add_custom_command() target? qt4_add_resource() doesn't seem to work as it expects non-generated files. Thanks, Eric. ___ Powered by www.kitware.com Visit other Kitware open-source pro

Re: [CMake] Visual Studio: release builds with "Generate Debug Info" enabled

On Tue, Jun 02, 2009 at 04:05:39PM -0400, John Drescher wrote: > How about using the RelWithDebInfo build that CMake generates? Good idea. I'll look into this. Thanks, tyler ___ Powered by www.kitware.com Visit other Kitware open-source projects at ht

Re: [CMake] Visual Studio: release builds with "Generate Debug Info" enabled

On Tue, Jun 2, 2009 at 3:54 PM, Tyler Roscoe wrote: > We build the Release versions of our libraries with Debug info enabled. > > In Visual Studio, you enable this by setting > Properties->Linker->Debugging->Generate Debug Info to Yes. > > All this really does is add /DEBUG to the link flags for t

[CMake] Visual Studio: release builds with "Generate Debug Info" enabled

We build the Release versions of our libraries with Debug info enabled. In Visual Studio, you enable this by setting Properties->Linker->Debugging->Generate Debug Info to Yes. All this really does is add /DEBUG to the link flags for the library. So I added "/DEBUG" to the LINK_FLAGS_RELEASE prop

Re: [CMake] win32 and x64 in the same generator?

Mike, Philip, Sergey, John, Thanks for the insights. They will be useful in calming our Windows developers. Mike, On Mon, Jun 01, 2009 at 11:45:38PM -0400, Mike Jackson wrote: > > Two things come to mind: > > > > 1. find_library() (i.e. dependencies).. How would you pick 64-bit vs. > > 32-bit? >

Re: [CMake] Convenience libraries support

On Tuesday 02 June 2009, Francis Leblanc wrote: > Hi everyone, > > Convenience libraries support in CMake was needed for our project, so I > decided to take a look at the source code and see what could be done. I've > managed to make it work relatively quickly, thanks to the comments and the > way

[CMake] Convenience libraries support

Hi everyone, Convenience libraries support in CMake was needed for our project, so I decided to take a look at the source code and see what could be done. I've managed to make it work relatively quickly, thanks to the comments and the way the code is written !! :D I don't know if it's supported

Re: [CMake] How do you make a 64-bit NSIS installer for Windows?

The functionality needs to be added. Patches attached to feature requests in the bug tracker are always welcome. :-) Basically, we need some bit-ness detection code in the Modules/ NSIS.template.in file. On Tue, Jun 2, 2009 at 9:21 AM, Keith Gardner wrote: > My company is trying to package our

Re: [CMake] How do you make a 64-bit NSIS installer for Windows?

Thanks for the quick reply. I created a feature request in mantis. http://public.kitware.com/Bug/view.php?id=9094 Keith -Original Message- From: David Cole [mailto:david.c...@kitware.com] Sent: Tuesday, June 02, 2009 8:37 AM To: Keith Gardner Cc: cmake@cmake.org Subject: Re: [CMake] How

[CMake] How do you make a 64-bit NSIS installer for Windows?

My company is trying to package our software on Windows using NSIS in 32-bit and 64-bit but the install path always assumes that the package is 32-bit. If you are on a 64-bit machine, 32-bit and 64-bit NSIS installers use "C:\Program Files (x86)" as the install path. The proper way for a 64-bi

Re: [CMake] win32 and x64 in the same generator?

> Our developers are used to a single .vcproj that knows how to build both > 32-bit and 64-bit versions of libraries. Under CMake, 32-bit and 64-bit > are considered separate platforms with separate generators and requiring > separate binary directories. > > Conceptually and as a build engineer, th

Re: [CMake] Problem with ASM and COMPILE_DEFINITIONS

Done. See http://www.cmake.org/Bug/view.php?id=9092 Best regards, Marcel Loose. -Original Message- From: Alexander Neundorf Reply-to: a.neundorf-w...@gmx.net To: cmake@cmake.org Subject: Re: [CMake] Problem with ASM and COMPILE_DEFINITIONS Date: Fri, 29 May 2009 00:20:40 +0200 On Wednes

Re: [CMake] win32 and x64 in the same generator?

Philip Lowman wrote: On Mon, Jun 1, 2009 at 6:29 PM, Tyler Roscoe > wrote: What are the pitfalls or difficulties in supporting this sort of "cross-compiling" in Visual Studio? Two things come to mind: 1. find_library() (i.e. dependencies).. How would you pick