Re: [CMake] Prevent libraries from linking twice during LLVM build

Thanks a lot for the context Michael ! On Thu, 20 Apr 2017 at 22:03 Michael Kruse wrote: > The cmake mailing list may not have sufficient context, so let me add > some details. > > Polly is an extension library for LLVM. Both can be configured in > multiple

Re: [CMake] Need code review of my android toolchain file

I guess the only feedback I really would like is if the path normalization I'm doing for CMAKE_ANDROID_NDK is necessary (converting backslashes to forward slashes). Will CMake translate the backslashes properly? Sometimes I use CMAKE_ANDROID_NDK in custom commands and custom targets to build

Re: [CMake] Need code review of my android toolchain file

Hi Robert, I would use file(TO_NATIVE_PATH "${_dir}" _dir) and file(TO_CMAKE_PATH "${_dir}" _dir) hope that helps, Cheers, Volker Am 21/04/2017 um 15:45 schrieb Robert Dailey: I guess the only feedback I really would like is if the path normalization I'm doing for CMAKE_ANDROID_NDK is

[CMake] fftw library in cmake

Hi all , Below is my CMakelist.txt. I'm getting an error as mentioned below . I'm not to rectify it . Could anyone help me out here please ? ​CMAKE_MINIMUM_REQUIRED(VERSION 2.8) PROJECT(PROSE) ​ ExternalProject_Add(project_fftw #GIT_REPOSITORY https://github.com/FFTW/fftw3 URL

Re: [CMake] fftw library in cmake

On 04/21/2017 03:40 PM, aishwarya selvaraj wrote: add_library(fftw STATIC IMPORTED) [...] TARGET_LINK_LIBRARIES(prose fftw ) [...] make[2]: *** No rule to make target `fftw-NOTFOUND', needed by `prose'. Stop. You are creating an IMPORTED target "fftw" but you aren't populating its

Re: [CMake] fftw library in cmake

Thanks Nils for the input . On Fri, Apr 21, 2017 at 7:19 PM, Nils Gladitz wrote: > On 04/21/2017 03:40 PM, aishwarya selvaraj wrote: > > add_library(fftw STATIC IMPORTED) > > [...] > > TARGET_LINK_LIBRARIES(prose fftw ) > > [...] > > make[2]: *** No rule to make target

Re: [CMake] Overriding the include path, library path of OpenSSL, Zlib and libcurl

Thanks for the help.  I will try that. Alex Chen From: Michael Ellery Date: Thursday, April 20, 2017 at 8:13 PM To: Alex Chen Cc: CMake Subject: Re: [CMake] Overriding the include path, library path of OpenSSL, Zlib and

[CMake] add_custom_command on test input files

Hello, for my project I have a sub dir with test case which feeds the tests '*.input' and allows to check to output '*.expected'. For documentation purpose, I have a python script which generates a TestMatrix.rst file. Using CMake I have: dir structure: $root/{src,include,utils,test}

Re: [CMake] Overriding the include path, library path of OpenSSL, Zlib and libcurl

Although cmake uses the path I supplied for OpenSSL and Zlib, I do not see the –I flag being used in compiling the code. (I set VERBOSE=1 to make to see what it does.) When I run ‘ldd’ against the resulting .so files, reference to libssl.so or libcrypto.so is empty, i.e ‘libssl.so => not

[CMake] Trouble with FindPNG module

I'm running CMake 3.8.0 on Ubuntu 14. I invoke the following: find_package(PNG REQUIRED) Which gives me the output in CMake: Could NOT find PNG (missing: PNG_LIBRARY) (found version "1.2.50") The CMakeCache.txt file has these variables set:

Re: [CMake] Overriding the include path, library path of OpenSSL, Zlib and libcurl

after find_package is invoked, several variables will be set. You use these to augment your compiler and linker information, e.g.: target_include_directories(mytarget $ZLIB_INCLUDE_DIRS) target_link_libraries(mytarget $ZLIB_LIBRARIES) …and so on for other modules you find (OpenSSL, for

Re: [cmake-developers] Proposal to disable link depends inference.

On 04/20/2017 05:16 PM, Matthew Hanna (BLOOMBERG/ 731 LEX) wrote: > avoid adding the external to external edges > https://gitlab.kitware.com/mhanna21/cmake/commit/2c7d2e33b6218e58f88957fb793ce0a781ec76aa That sounds good. From the patch: > + if (this->EntryList[depender_index].Target || >

[Cmake-commits] CMake branch, master, updated. v3.8.0-841-g59f07ef

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 59f07efd592330be3018fcaa253498475055a4af (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-853-g1d8f0f9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 1d8f0f918178c50e8ef66b01546f34cd2a126a6d (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-831-g2b7aecb

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 2b7aecba1663f86148b8c2f1033cfcbd87453ad3 (commit) via

Re: [cmake-developers] Support for unified headers in Android NDK

Thanks Florent! Let me know if you need any help, especially testing. I have a real world use case for this at $DAYJOB. On Thu, Apr 20, 2017 at 4:14 PM, Florent Castelli wrote: > I just came back from some holidays now, I'll try to update the MR with the > latest

[Cmake-commits] CMake branch, master, updated. v3.8.0-856-g294cf94

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 294cf948dc37799e1980685afbf1fa585ad5b0fb (commit) via

[Cmake-commits] CMake branch, release, updated. v3.8.0-8-g08c99c9

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via 08c99c92532aaa54cf716ce07bc241ae1d2e997b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.8.0-857-ge9d1ca7

_VERSION_MINOR 8) -set(CMake_VERSION_PATCH 20170421) +set(CMake_VERSION_PATCH 20170422) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [cmake-developers] [Feature Request] Fortran standards compliance for various compilers

On Thu, Apr 20, 2017 at 4:12 AM, Alan W. Irwin wrote: > On 2017-04-19 07:27+0200 Rolf Eike Beer wrote: > >>> What would really be useful is a list containing >>> what Fortran features from the Fortran 2003 and 2008 standards that the >>> given Fortran compiler

[cmake-developers] Adding Microsoft MPI Fortran support in FindMPI

Hi folks, I’d like to implement support for MSMPI’s Fortran API in FindMPI so that it could be used to build ScaLAPACK and others. However, I’m looking for a bit of guidance on how to do this. The Fortran 90 interfaces are contained in a file called mpi.f90 in the MSMPI include folder. This