Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?

Konstantin Podsvirov wrote: > The data now includes subfolders Help, Modules and Templates. > Why are Help (the rst set of files)? As they are used after installation? Yes. The Help files need to be mandatory too. They are used by cmake for showing documentation on the command line like cmake

Re: [cmake-developers] OpenBSD and srand()/rand() changes

Yes, setting an explicit seed should make subsequent calls to random be deterministic... On Wed, Dec 10, 2014 at 9:50 AM, Rolf Eike Beer wrote: > Am 10.12.2014 15:38, schrieb Ben Boeckel: >> >> Hi, >> >> It appears[1] as though OpenBSD has changed srand and rand which we use >> in CMake for stri

Re: [cmake-developers] FindMPI take 2

Hi KT, > In general, I think this is a good idea because I have encountered situation > were the cmake compiler was a different flavor (intel, gnu, pgi, etc) than > the selected mpi compiler wrapper. However, if the chosen mpi compiler > wrapper is the same as CMAKE__COMPILER, we don't need th

Re: [cmake-developers] FindMPI take 2

Alin Elena wrote: > In addition to that I have noticed that in the interrogate > function we never check that we can actually generate a binary > with the findings, shall we have a try_mpi_compile at the end > of interrogate function? In general, I think this is a good idea because I have encoun

Re: [cmake-developers] [PATCH] VS, WINCE: Fix entry point for Unicode builds

> > I think that would be the best approach. If you work on it, please ensure > the implementation supports all Windows toolchains on all generators, or at > least those combinations that already support WIN32_EXECUTABLE. > I had a look trough the code. I found that the VS6 generator also sets

[cmake-developers] [CMake 0015299]: CMakeExpandImportedTargets does not support generator expression TARGET_PROPERTY w/o target specified

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15299 == Reported By:Paweł Stankowski Assigned To:

Re: [cmake-developers] FindMPI take 2

Hi Kelly > I have been looking into this. For my setup, I found it useful to compare > the CMAKE__COMPILER to the list of known mpi wrapper names and prepend > _MPI_${lang}_COMPILER_NAMES with CMAKE__COMPILER so that the remaining > logic in FindMPI.cmake chooses the user supplied compiler/mpi-

Re: [cmake-developers] FindMPI take 2

Hi Brad, >> 0001-correctly-detect-MPI-linker-flags-for-Intel-MPI-mayb.patch > > Thanks. That adds a block much like one above it. Can the preceding > block be modified to match both -Wl, and -Xlinker? Something like: > > -string(REGEX MATCHALL "(^| )-Wl,([^\" ]+|\"[^\"]+\")" > MPI_A